Fix broken .NET Framework source stepping caused by 4.5 and 4.0 assemblies having the same strong name.
.NET Framework source stepping is not working with 4.0 or 4.5 targeted applications, because version 4.0 and 4.5 use the exact same strong name for the assemblies. The decision to skip versioning and do an in-place update to 4.5 breaks Visual Studio, let alone everyone else's applications. What a terrible idea! Do proper versioning.
Thanks for the suggestion. We’ve now enabled source stepping for .NET Framework 4.5 RTM. For more information, see: http://blogs.msdn.com/b/dotnet/archive/2012/08/15/announcing-the-release-of-net-framework-4-5-rtm-product-and-source-code.aspx
Richard Hein commented
David, installing .NET 4.5 with Visual Studio 11 Beta prevents you from being able to step into .NET 4.0 Framework source. You won't be able to do it with VS2010 anymore either. Because .NET 4.5 assemblies replace 4.0 it breaks the ability to do debug .NET 4.0 projects. It doesn't work for 4.5 either, for the reason you gave, but it also breaks it for .NET 4.0.
David Kean commented
Richard, can you provide more information on what you mean by this? Source stepping isn't/shouldn't be broken because the assemblies have the same strong name (the debugger can handle this situation), it's not working because we typically don't publish source for pre-releases.
David Kean (MSFT)