If you’re trying to access a class library (.NET Standard) from a traditional console application (in VS2017 those can be found under ‘Windows Classic Desktop’) you will run into problems; which can feel a little strange for something that was pretty simple in VS2015 and earlier. You can add a reference to the class library project (Resharper will even volunteer to add the dependency / namespace reference if you don’t already have it). But the . . .
The title pretty much says it all, there is no way to open an MVC2 project within Visual Studio 2012, there is no “auto-upgrade” path either! If you attempt to convert a solution containing an MVC2 project you will probably see the following error message: Subtype: ‘{F85E285D-A4E0-4152-9332-AB1D724D3325}’ is unsupported by this installation. If you do, then the only real solution appears to be graft the existing MVC2 project into an empty MVC3 or MVC4 project . . .
Not sure that this post really needs anything more than the title. If you are upgrading a Silverlight project from VS2008 or VS2010 be aware that VS2012 only supports versions 4 & 5 of Silverlight. If you need to update the solution/projects to use them in VS2012 I’d recommend upgrading to at least Silverlight 4 first in your existing Visual Studio and then once it’s working upgrade the solution/projects to VS2012 so you’re only tackling . . .
We’ve recently upgraded to Visual Studio 2012 from VS2008 and switched over to using NuGet rather than direct project references for our third party tools. Everything worked as planned until we checked the solution into source control and the personal build for TeamCity kicked off. Almost straight away the build fell over with the following error message: D:TeamCitybuildAgentworke6ae794aab32547b.nugetnuget.targets(102, 9): error MSB4067: The element beneath element is unrecognized. Project BJ.Core.sln failed. Our projects were still targeting . . .
I ran into an interesting problem today when upgrading a visual studio 2008 project to visual studio 2012, whilst trying to leave the targeted framework to .NET 3.5. Each time I tried to open the solution all my test projects automatically upgraded to .NET 4.0 regardless of what I did. It was impossible to downgrade the project using either the project property page or manually editing the project file. I’d make the change and then . . .
Today Jetbrains announced on their blog that they’ve released a resharper nuget package that will obtain project references via nuget, rather than making direct references to the locally installed code. As we are currently in the early stages of transitioning from VS2008 to VS2012 we aren’t ready to start using NuGet(*) but I think I’ll be grabbing this plugin for when we do. (*) In my last role we were using VS2010 and making heavy . . .
Just a word of warning: Windows NT and Windows Server 2003 do not support .NET 4.5 – you can not install the framework onto these systems. So if you are building in visual studio 2012 and have to support Server 2003 (or earlier) then you must remember to target .NET4.0 (or lower) in your project(s) otherwise you will not be able to run them on the target system. That would be a really bad thing . . .
One thing I’ve found over time is you can never find licensing details for VS and SQL products when you need them, so here’s the link for VS2012 Licensing details I quite like what Microsoft is doing with these white papers, the use case examples are really useful and answer most usage questions.
If you’re using WIX and you’re adding components to the product file by hand then you’ve probably found yourself creating and cutting/pasting a lot of GUIDs which can be a real pain and productivity killer. There is the “Create GUID” menu option under tools but that still requires calling and then cutting / pasting. The other day one of the other members on our team came up with these steps to create a macro that . . .
When looking to automate a TFS2010 build one of the first issues that most people seem to encounter is that all the binaries of each project in a solution end up in the same “bin” directory. The forum post TFS 2010 BUILD SERVER: Can not keep folder tree in the drop location ? details the solution; which is changes to both the CSPROJ file and the workflow template that is called by your build. Note: . . .