Team,
I have recently converted my project from .net framework version 4.0 to 4.6 using VS 2017. All is ok when i do a manualy build on my local computer.
But when i checkin and do a CI build, its gives the following error
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (3075): Could not find file 'obj\Release\MyApplication.exe
I am not sure what it is...i have got 25 projects under a solution and there is nothing called as Myapplication.exe.
Can anyone please help me ?
Related
im trying to compile a solution in MS VS 2012 which was original written in MS VS 2005 (? I'm not sure but it is a much older version).
The compiling and linken works without any problems. But when I try to start the exe I'll get an error which says:
"msvcp80d.dll is missing from your computer"
I tried to install the old vc++ redist package, but this ships only with non debug version of the library.
Anyone knows how to force VS to link against a newer version of msvcp80d.dll. (should be msvcp110d.dll in this case). I already updated the complete solution without success. The plattformtoolset is set to "Visual Studio 2012 (v110)" but this seems to be ignored.
I would appreciate any help. Thanks in advance!
I have a solution with a number of C# projects targeting .Net 4.6 and one native C++ project (no CLR). After using the solution with VS2015 I now get errors when trying to open the solution in VS2013 with half the projects failing to load.
The native C++ project and some of the C# projects give the error:
error : A numeric comparison was attempted on "$(TargetPlatformVersion)" that evaluates to "10.0.10069.0" instead of a number, in condition "'$(TargetPlatformVersion)' > '8.0'". C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets
I'm not sure why some projects correctly load and others don't, however, it does look like all C# projects which reference NuGet packages fail.
Is there a way to fix these errors and allow the solution and projects to be opened in both VS2013 and VS2015?
After trying out various changes to project files I found that removing the following line from the native C++ project then allowed all projects in the solution to load correctly.
<TargetPlatformVersion>10.0.10069.0</TargetPlatformVersion>
However, after loading I then found that I couldn't build the native project because of the error:
error MSB8020: The build tools for v140 (Platform Toolset = 'v140') cannot be found.
Even though the vcxproj specifies ToolsVersion="14.0" it appears that Visual Studio 2013 will use 12.0 for C++ projects. In the project's properties the Platform toolset says v140 (not installed). Changing this to Visual Studio 2013 (v120) would allow the project to build in both VS2013 and VS2015, though obviously using the older 12.0 tools rather than 14.0. Instead I added the following lines to my project file:
<PlatformToolset Condition="'$(VisualStudioVersion)' == '12.0'">v120</PlatformToolset>
<PlatformToolset Condition="'$(VisualStudioVersion)' >= '14.0'">v140</PlatformToolset>
Now VS2013 will use the v120 Platform toolset and VS2105 (and later) will use v140.
After building with VS 2015 the project file may have a TargetPlatformVersion and/or WindowsTargetPlatformVersion line added. If the value is 10.0.10240.0 or another Windows 10 version then the project won't load in VS 2013 as it doesn't like the non-decimal value. This can be fixed by changing the value to 8.1, telling Visual Studio to use the Windows Kit for Windows 8.1 rather than Windows 10.
Note:
Even though you can target .Net 4.6 with VS2013 it doesn't understand C# 6 so will give errors if you try and use any of the new language features. Similarly, targeting v120 for the C++ project prevents you using newer language features supported in VS2015.
I am new to C++ programming, so I thought to get into it by getting familiar with SFML.
I downloaded Visual Studio 2013 Express Windows Desktop.
Then I realized that there is no SFML for VS2013.
So I have to compile/built it for me and I downloaded CMake.
When compiling it regarding some of the many tutorials on the internet, I get to the point, when I have to build in VS2013 with the "SFML_STATIC" flag.
Thus before, I build it successfully for the shared libs.
When I generate in CMake against the generator "Visual Studio 12 2013", it will create five projects:
sfml-audio.vcxproj
sfml-graphics.vcxproj
sfml-network.vcxproj
sfml-system.vcxproj
sfml-window.vcxproj
It starts off with a problem that 4 of 5 projects are corrupt, so I have to manually fix the .vcxproj files.
After that I reload the projects and I start building the solution.
I do get linker errors, telling me he/she/it cannot find several files:
opengl32.lib;winmm.lib;gdi32.lib;ws2_32.lib;
and some SFML specific files.
I have found out that those files are in a location where in VS2013 the variable #(WindowsSdkDir) points to. But still those .dlls are note found, see
I also have found that there are some issues with this for VS2013 targeted at MS.
Does anyone know how to fix this? Did anyone built it successfully?
Many thanks in advance. I appreciate your help.
I'm trying InstallShield project to create an installations using Visual studio TFS 2012. But, setup file is not being generated. When I looked into the error log, it says "isproj is not supported by MSBuild and cannot be built"
Let me know what is the fix for this issue.
I am facing a problem in an attempt to debug the code in Visual Studio 2012. I have series of the class files and the Asp.Net pages in a single solution file. The Asp.Net pages call functions in the class libraries and get the required details.
Everything worked well until I upgraded my license from Visual Studio 2010 to Visual Studio 2012. The problem is that reference to the assemblies are lost and the build is failing. Additionally the Dlls after the compilation of the individual class file project are deleted.
Please let me know if someone has faced similar problem and resolution.
Thanks,
Yagya