Convert Microsoft Visual Studio applications to version 2012
When Microsoft releases a new version of Visual Studio developers would like to use the new features of the new IDE. Usually the new version of Visual Studio converts the solution and project files to a new format to be able to save the new settings of…
Microsoft Visual Studio solution folder structure for easy conversion to the new version of the IDE
Microsoft releases a new version of Visual Studio every 2-3 years, but most of the enterprise applications have to be operational for years. Many companies developed applications in earlier versions of Microsoft Visual Studio ( VS 2003, VS 2005, VS…
Yellow exclamation point next to a project reference in Microsoft Visual Studio 2012 after conversion to a newer version of the IDE
When you convert a solution to a new version of the Microsoft Visual Studio IDE you can see yellow exclamation points next to some project references. When you build the solution you also get errors like the following: Error, The type or namespace name…
How to handle “The target version of the .NET Framework in the project does not match…” warning message in Microsoft Visual Studio
When you build the setup project in Microsoft Visual Studio 2010 you receive the following warning message: The target version of the .NET Framework in the project does not match the .NET Framework launch condition version ‘.NET Framework 4 Client…
How to solve “The version of the .NET Framework launch condition ‘.NET Framework 4’ does not match…” warning in Microsoft Visual Studio
When you build the setup project in Microsoft Visual Studio 2010 you receive the following warning message: The version of the .NET Framework launch condition ‘.NET Framework 4’ does not match the selected .NET Framework bootstrapper package.…
Solving “The type or namespace name … could not be found” error in Microsoft Visual Studio
When you compile a .NET 4.0 C# application the following error message appears: The type or namespace name … could not be found (are you missing a using directive or an assembly reference?) There is also a warning message : The currently targeted…