My latest in a series of the weekly, or more often, summary of interesting links I come across related to Visual Studio.
Jason Kresowaty has done a lot of work putting together a good overview of writing your own custom FxCop rules. His tutorial covers the current 1.36 beta.
Carlos Quintero has added two good posts to his blog on VS Extensibility. The first is an explanation of how to tell that a project is in debug or release configuration. Carlos explains the differences between C# and VB.Net projects in this respect as well. The second is how to execute a build for all projects in a solution from within a macro or add-in.
The VS Code Analysis Team explained how to turn off FxCop checking for generated code. This is specific to the new 1.36 version.
Scott Guthrie shows the new support in Expression Blend for Silverlight 2.0. Tutorial goodness.
The Windows SDK Team Blog has a discussion of how to integrate the SDK with Visual Studio 2008 using the new SDK Configuration Tool.
The VS Extensibility Team has released PowerCommands for Visual Studio 2008. The tool adds new menu items in various places in Visual Studio. The Visual Studio Gallery video on Channel 9 has a brief demo of this tool at the end.
Via Jason Haley, here is an interesting post about Authenticode signing assemblies and what the framework does with those assemblies. Speaking of Authenticode, I recently had to go through the process of buying my own certificate and Andy Brice recently posted about certificate authorities and the cost of certificates. His post hit home in a lot of areas and was humorous in others. For full disclosure purposes, I went with Comodo for my cert.
VS Knowledge Base stuff:
- Visual Studio 2005 can break hard links to files when you edit them.
- ERROR_CODE: (NTSTATUS) 0xe06d7363 – <Unable to get error code text> – may mean a corrupt .Net install.
- You can get trace output on a machine where VS is not installed.
- Many fixes available for Visual Studio 2005 Team System Database Professional.
- VS 2005 may crash when compiling a large VB project.
- When a project is on a mapped drive, Edit and Continue does not work.