Warning: strpos(): needle is not a string or an integer in /customers/a/f/c/fjorden.se/httpd.www/joel/index.php on line 31 Warning: strpos(): needle is not a string or an integer in /customers/a/f/c/fjorden.se/httpd.www/joel/index.php on line 37 Warning: strpos(): needle is not a string or an integer in /customers/a/f/c/fjorden.se/httpd.www/joel/index.php on line 43 Blog by Joel Fjordén a.k.a. Will o Wisp
Developer Express Writes About Code Style Enforcer 
Wednesday, August 2, 2006, 01:06 PM - Code Style Enforcer
It always feels good when someone gets their eyes on something that you have developed. It is even more fun when it is the company behind the framework you are using.

Developer Express, the company behind DXCore, has posted an interview about the development of the Code Style Enforcer plug-in.

Read the whole blog post at the community site for Developer Express.

Code Style Enforcer – A DXCore Plug-In for Visual Studio 
Friday, July 28, 2006, 05:50 PM - Code Style Enforcer
Now it is time to finally make my DXCore plug-in available to the public. For those of you who do not know what DXCore is, I suggest you visit Developer Express which is the company behind this incredible extensibility framework for Visual Studio .NET.

So what does this plug-in do? Well, it checks the code against a configurable code standard and best practices. It is developed for C#, but some of the rules will probably also work for VB .NET.

Some of you might ask yourself right now, "Why the heck should I want to use that"? A code standard, huh, what is that about?

So let me tell you about the current project I am working in and perhaps you might want to give it a shot and try it out before you ask yourself these questions.

Far from everyone followed the code standard before, some did, but it was not always The Code Standard, but instead sometimes their own. The reason for not following The Code Standard was not because they did not want to, but simply because they did not see that they actually violated some rules.

Now with this plug-in all code statements that violate a rule in the code standard are underlined with red, and suddenly everyone wants to correct it, since nobody want to commit code that simply does not "look nice".

Some were a little skeptical about it at first, but now after trying it for a few months, my impression is that everyone really likes it and it has become a "standard tool" in our development tool portfolio.

For more information about this plug-in, visit the project page "Code Style Enforcer". Here you will find all releases, installation instructions and some other might-be-good-to-know-about information.

Please try it out and do not hesitate to give me feedback, be it good or bad.

Code Style Enforcer Screenshot
8 comments ( 1329 views )   |  related link