Stylecop, vb.net and VS2008 slowness

I was all excited to discover Stylecop, a tool that integrates with VS2005 and/or VS2008 and verifies that your C# code follows the style guidelines your team/project/company has established. It is similar to FxCop. Unfortunately it does not work with VB.net and despite the pronouncements from Microsoft, there is a step-child treatment meted to VB.Net. And the general perception is C# is a better, and vb.net programmers are inferior. This post is not about that.

Stylecop works great on your C# code and does not seem to affect the IDE in any way. However, when editing VB.Net source, the IDE is sluggish. It’s as if you are logged onto a remote machine on another continent.

Uninstalling Stylecop resolved the slugishness. Don’t understant why Stylecop which does not even understand VB.Net source should cause the IDE issues. Maybe it’s trying to figure out the code??

Advertisements

About Ramesh Sringeri

Yet another chaos monkey. View all posts by Ramesh Sringeri

2 responses to “Stylecop, vb.net and VS2008 slowness

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: