#VISUAL STUDIO 2012 BUILD TOOLS V110 UPDATE#
By default, the toolset for VC++ projects is set to Visual Studio 2012 (v110), but after installing Update 1, a new toolset called Visual Studio 2012 - Windows XP (v110_xp) is available (installed side-by-side). After great demand, Microsoft has brought back the support for those operating systems in Update 1. The RTM release of Visual Studio 2012 has dropped support for targeting Windows XP and Windows Server 2003 for VC++ projects, requiring minimum Windows Vista and Windows Server 2008. To fix this, the most appropriate solution is to use $(OutDir)$(TargetName)$(TargetExt) as the Output file and make the appropriate settings of these properties under the General page. To correct this, please make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile). This may cause your project to build incorrectly. 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\(1139,5): warning MSB8012: TargetName(MFCApplication1) does not match the Linker's OutputFile property value (MyAppD).
That triggers some warnings:ġ>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\(1137,5): warning MSB8012: TargetPath(D:\Marius\VC++\MFCApplication1\Debug\MFCApplication1.exe) does not match the Linker's OutputFile property value (D:\Marius\VC++\MFCApplication1\Debug\MyAppD.exe). I used to do settings like $(OutDir)\MyAppD.exe in a Debug configuration and $(OutDir)\MyApp.exe in a Release configuration. One of the issues that I encountered was caused by the fact that I used to explicitly specify the Output File in the Linker settings.
This can however lead to some warnings or even errors in the build. vcxproj, but there is an automatic conversion from the old. With this switched, the project files also changed to an MSBuild format. In Visual Studio 2010, VC++ moved away from VCBuild and started using MSBuild. The first most important issue for VC++ projects is that the format of the project files has changed. Therefore, if you are already familiar with this version, you probably know at least some of them. NET 4.5, but were actually introduced in Visual Studio 2010 and. Some of the issues mentioned in this article are not specific to Visual Studio 2012 or. Of course, these are not all the problems, but some that I can share from experience. NET 4.5, it is about problems you might encounter when you migrate. This article is not about new features in Visual Studio 2012 and.
Migrating a large application (around 120 projects, 4MLO) written with C++, C#, C++/CLI and involving different technologies and frameworks, I have stumbled on different problems that I want to share, hopefully to make the transition easier for others. This article is a collection of tips and tricks for migrating projects from Visual Studio 2008 to Visual Studio 2012.
0 kommentar(er)
