NET 2.0 redistributables is insufficient. NET 2.0 in VS 2012, we still need to have C++ tools from VS 2005 or 2008 installed on the machine they’re not included in VS 2010, 2012, or 2013. It’s important to note that, even though we’re targeting. Now, if you now open the project properties and look at “Common Properties/Framework and References,” you’ll see that the targeted framework has been changed to .NET 2.0. Save away the file, close the editor window, right-click on the project node in Solution Explorer, and select “Reload.” (You can also use Notepad or any other editor to do this.) Look for the element (or add it to the “Globals” property group if it’s not there already), and change its value from v4.0 to v2.0. First, unload the project by right-clicking it in the Solution Explorer and selecting “Unload.” Then, right-click on the project in Solution Explorer and select “Edit.” The project (an XML file) is displayed in an editor. The targeted framework property is also a read-only field, so despite the fact that Visual Studio is supposed to support multi-targeted C++ projects, you can’t actually change the target framework inside Visual Studio.įortunately, there’s a way around this problem you need to edit the text of the project file directly. VS 2012 “helpfully” and silently not only upgraded our project from VS 2008, but also from.
Even though we upgraded a 2.0-targeted project, the targeted framework was. The problem was caused by issues with both managed multi-targeting and native multi-targeting in C++.Įxamining the C++ project properties, under the “Common Properties/Framework and References” header, there is a “Targeted Framework” property.
Examination of the DLLs showed that, despite their referencing 2.0 libraries, they were. NET 2.0 libraries, BadImageFormatException was thrown when they were used. The upgraded C++ projects, on the other hand, had problems: although the generated DLLs referenced. The C# projects upgraded without any problem, and without any additional input from the developers. (Note that, even though we’re using VS 2012, everything below holds true for VS 2013, too.) NET code contains both C# and C++ projects. For a long time, we’ve done these 2.0 builds on Visual Studio 2008, but we decided to use Visual Studio 2012 for both 2.0-targeted and 4.0-targeted builds, making use of VS 2012 multi-targeting capabilities.
NET side components to use Visual Studio 2012. If you’re not facing this problem, you have our permission to skip this post. We hope that our suggestions will save you a lot of time and angst. The following is a public service announcement intended to help anyone who has a C++ project that was created with an old Visual Studio version like VS 2005 or 2008, and now wants to keep editing it with a more modern Visual Studio.
0 kommentar(er)
