|
SharePoint Development Help
is Here!
| A great new product is
now available to SharePoint developers.
|
 |
The utility is named
SP-Lint+ and
it is a similar to the 'lint'
tools that 'C' language developers
have relied upon for years, but
it is designed for
SharePoint feature developers.
Since the C language was intended
to be more-or-less a portable assembly
language, lint
utilities were developed to identify
non-portable syntax or constructs.
Why do SharePoint
developers need a lint utility? Well
its not for the portability aspects
of SharePoint
features, but rather because the
development and maintenance of features
can be helped with a
static code analysis tool similar
to lint.
What is static code analysis and
how does it help? Static code analysis
performs checks on
your project source files to identify
inconsistencies and does not require
compiling or
executing your code. SharePoint
feature creation is complex, requiring
a number of artifacts
(configuration files, CAML definitions,
a DDF file, images, etc.) which
together comprise
your feature. |
Download SP-Lint+
Beta Now!
Questions?
Read the the FAQ. |
Simply put, SP-Lint+ is designed to
help spot and track down feature
inconsistencies or
configuration errors.
Features:
- Small application size and
simple installation
- Quick execution times: typically
runs in less than a second
- Implements over 600 validations.
- Validates most properties
of the 46 Element schemas,
including:
- List Template Files
- List Instances
- Modules
- Field Definitions
- Event Registrations
- Custom Action
Definitions
- Content Type
Definitions
- Delegate Controls
- Feature/Site
Template Associations
- Workflow Definitions
- Content Type
Bindings
- Document Converters
- Verifies all Feature XML
properties
- Analyzes both C# and VB-based solutions.
- Compares the feature
token keys to those
identified in the XML
configuration
- Identifies obsolete element
attributes
- Identifies conflicting configuration
attributes
- Automatically identifies
features if no manifest is present
- Outputs results in either
plaintext or XML-file formats
- Comparison of DDF contents
and solution artifacts (in development)
- Can be executed as a post-build
step or from MSBuild
| 
