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.

FxCop Rules Join the Pipeline Builder for System.AddIn

Posted by Jonathan Allen on Jul 14, 2008

Sections
Process & Practices,
Architecture & Design,
Development
Topics
Code Analysis ,
.NET
Tags
FXCop

In .NET 3.5 Microsoft created a set of guidelines and libraries specifically for creating extensible applications. Often referred to by its namespace identifier, System.AddIn gives developers the tools they need to support third-party extensions without jeopardizing the security and robustness of their application as a whole.

Much of this is accomplished through the use of AppDomains and rigid communication pipelines. However, building all of the boilerplate needed to make this work is rather daunting. Hence the release of the Pipeline Builder. But while it does give developers a leg up, it has no way to warn them when they are doing something wrong.

This is where a new set of FxCop rules for AddIns come into play. While they certainly won't catch everything, they should point developers in the right direction. These rules are only available in source code format and fall under the "Microsoft Limited Public License".

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

No comments

Watch Thread Reply

Educational Content

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.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

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.