New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
News
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
SDK for StyleCop Released
Posted by Jonathan Allen on Sep 02, 2008
Unlike Microsoft's FXCop, which was largely celebrated as an important step towards improving the consistency and quality of .NET code, StyleCop has been viewed with much suspicion. The main difference between the two is that FXCop focuses on compiled code from any .NET language while StyleCop works solely against C# source code.
The biggest complain about StyleCop is that its recommendations are mainly based in opinion. While some of the guidelines in FXCop are subjective, most are grounded in sound logic based on a deep knowledge of how the CLR works. StyleCop, on the other hand, is mostly about hotly debated issues like how many spaces to use for indention. Some are even downright contrary to standard practices like placing "using" statements inside namespaces.
With the release of the StyleCop SDK, developers can develop their own rules to supplement or outright replace the default ones. While in the long run developers are going to want to be able to simple configure the rules to match their company standards, this is at least a good temporary solution.
In addition to creating new rules, developers will find information in the SDK on how to integrate StyleCop in MSBuild tasks.
RelatedVendorContent
SCM best practices for multiple processes, releases & distributed teams
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
A Guide to Branching and Merging Patterns
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Of all the examples..
by
Francois Ward
Posted
-
Some are even downright contrary to standard practices like placing "using" statements inside namespaces.
Of all the examples that could be taken... I wouldn't be surprised to someday find this particular one as part of FxCop... While many of StyleCops rules are subjective (read: make people sad because their "flawless" naming conventions are not all that flawless, or are totally obsolete as they're simply ported from older environments with different restrictions and requirements), that particular one has to do with how the compiler works, and is meant to catch as many errors as possible at compile time and remove ambiguity.
The standard Visual Studio templates have never followed -any- convention, and contredict each other...thats not new.
1 comment
Watch Thread Reply