InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Spell Checker Added to Visual Studio 2008

Posted by Jonathan Allen on Sep 25, 2007

Sections
Process & Practices,
Architecture & Design,
Development
Topics
.NET ,
Code Analysis
Tags
Visual Studio Team System ,
FXCop

The Code Analysis team at Microsoft has decided to include FXCop's spell checker in Visual Studio 2008.

FXCop was originally designed as an in-house tool used by Microsoft to ensure a level of consistency across all .NET APIs. As such, many of the rules it enforces cover usability issues such as publically visible identifiers. Among these is a spell checker for identifiers, a necessary precaution against releasing a misspelled method name that can never be changed.

The public release of FXCop was so well received that in Microsoft decided to include the FXCop engine in Visual Studio 2005 Team Edition. When they did so, some rules were added while others, such as the spell checker, were removed. With VS 2008 some of those "lost rules" are coming back.

In addition to the spell checker itself, VS 2008 will have limited IDE support for custom dictionaries. A custom dictionary, in the form of an XML file, can be added to an entire solution or be assigned to specific projects within a solution. Because the raw XML file is being exposed, all of the advanced spelling rules can be modified as well. David Kean has promised to cover some of these in a future blog post. 

No comments

Watch Thread Reply

Educational Content

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.