.NET Framework SDK 4.5 changes Visual Studio 2010 Code Analysis and FxCop


There have been a few reports in the MSDN forums[1][2] that Code Analysis 2010 or FxCop 10 will trigger more often after installing Visual Studio 2012 or the .NET Framework SDK 4.5 along side Visual Studio 2010. There's also a bug on Connect[3][4] that follows this. This isn't caused due to Visual Studio 2010 suddenly using the 2012 version of FxCop or anything like that. It's actually caused by differences in the code being generated.

The issues that are detected, are actually issues that went undetected before due to the way .NET 4.0 generates code. In .NET 4.0 the code generated for a WPF custom control, for example, will have the [GeneratedCode] attribute at the class level. After installing the .NET 4.5 SDK this attribute is applied to the method level, instead. This post on the MSDN forums captures the differences really well:

Unless you're enforcing naming conventions using FxCop, the newer generated code will actually result in better checks of your existing .NET 4.0 code, but it will cause havoc when you're in a team that uses Visual Studio 2010 to edit the same controls, but some members also have Visual Studio 2012 installed, since the generated code will be different depending on who last edited the files. This is also going to be great fun when merging ;).

As to be expected, other tools that ignore Generated Code, such as StyleCop, Code Metrics and Code Coverage will be impacted by this change.

Visual Studio and Team Foundation Server 2012 Update 1 is now live


Just a quick note, Microsoft has released Visual Studio 2012 and Team Foundation Server Update 1. I'd been using the CTP ever since October and it adds a number of really nice features. Especially the improved support for testing SharePoint applications and other improvements to the Test Runner are what I was looking for, but there are a number of other improvements as well!

For the full details on what's new in TFS, check out Brian Harry's blog. And the new features in Visual Studio 2012 are detailed here.

Important remark: a new version of the Team Foundation Server Power tools is coming soon and the previous version contains features that may no longer work with TFS 2012 Update 1.

Windows 8 - Remote desktop tips and tricks


If you're using Remote desktop a lot, you'll find that a few things are changing with Windows 8. Here are a few tips and tricks to make your life easier:

  • On the Windows 8 Pro and Enterprise version the classic desktop version of Remote desktop comes pre-installed. To access it quickly hit Windows-Q, then type mstsc (that works on any machine, regardless of the users language).

Updating your Team Foundation Service Uri to the new tfs.visualstudio.com


Microsoft has decided that the Team Foundation Service (I'll start calling it TFSvc for short) has had enough testing and that it is now live and out of preview. They've also put it under a new domain name, tfs.visualstudio.com.

The old domain tfspreview.com will remain operational for a while, but in time it will be replaced. So there will come a time for you to update your Visual Studio TFS servers list with the new domain names.

If you have just one TFSvc project collection, that's easy. Just remove it from Visual Studio and add it again under the new name. But if you have a lot of Servers and ProjectCollections (like me) , then the following PowerShell script will make your life easier.


Most Reading