How can I do that ? Can I work in VS2010 IDE but have it compile with the VS C++ 6.0 compiler?
And can I work in VS2010 IDE and have it compile by using the the VS2008 compiler ?
you need the Daffodil extension
I know it is possible to achieve this with VS2008 IDE and I'm 99% sure it is the same with VS2010 (but I don't have one to try with). Make a batch file in which you first need to call VCVARS32.BAT file that is included with VC++ 6.0 and then start Visual Studio with "/useenv" switch. You will then use this batch file to start Visual Studio.
.bat file:
call "C:\Program Files\Microsoft Visual Studio\VC98\Bin\VCVARS32.BAT"
start "" "C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe" /useenv
NOTE: This is path to VS2008 IDE, you need to change path for VS10 by yourself (probably just needs changing number 9 to number 10). Also if you are using 64bit OS you will need to change both paths to use "Program Files (x86)".
Isn't possible.
You can use VS2010 C++ compiler to compile VS6 code w/o any problem.
take care about the solution will be migrated to new format (old one is saved as backup)
Here is link below which talks about visual studio 2008 but you can refer it to execute similar steps on visual studio 2010.
http://resnikb.wordpress.com/2009/10/28/using-visual-studio-2008-with-visual-c-6-0-compiler/
Related
I cannot execute my gtkmm-app any longer in visual studio 2012. It compiles fine but when executing it crasches. I get the error message that MSVCP100D.dll is missing.
I made this app in visualstudio 2010 last spring. OS was windows XP. No problem whatsoever.
Now I have visualstudio 2012 and windows 8.1 and get this error-message.
I dont know what to do? Is there a way to install MSVCP100.dll in the system-folder or could something be done in VS 2012?
I may underline that I just encountetred this problem when compiling and executing my gtkmm-app for the first time since the platform change and IDE-update. Ordinary console-applications no problems whatsoever.
If you also have time/knowledge - what is the purpose of this dll-file?
You are getting this error probably because you changed your compiler.
What you can do is to either recompile gtkmm with current Visual Studio or download pre-compiled binaries and rebuild your application.
Option 2 is to install Visual Studio 2010 back and forget about Visual Studio 2012.
If you want both latest Visual Studio and gtkmm 3 then...
It's not an easy task, and it's hard to answer your question in detail here, so
Here is an tutorial to let you get started compiling/installing gtkmm 3 in Visual Studio 2013 for Windows 7 and later:
This question already has answers here:
Visual Studio 2012 failing to detect Visual Studio 2008 build tools
(4 answers)
Closed 9 years ago.
I have Visual Studio 2008 installed on my machine and now installed VS2012. In the C++-project-settings of VS2012 I should now be able to change the platform toolset back to VC++2008 (V90), but there's only the new version VC++2012 (V110) available. Does anybody know the reason why my old installation of VS2008 is not recognized or how I can manually add the old platform toolset?
Thanks in advance.
The v90 platform toolset is part of VS 2010, so you must install both VS 2008 and VS 2010.
Well i have no experience with 2012, but when i used 2010 and 2008 combined i just had two different program files folders and so two different executable to start visual studio in the version i liked. Maybe this is of help to you just make 2 shortcuts ?
If you're sure you've got your VC2008 environment variables set properly, you can always hand-edit the .vcxproj.
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'" Label="Configuration">
<UseDebugLibraries>true</UseDebugLibraries>
<ConfigurationType>StaticLibrary</ConfigurationType>
<PlatformToolset>v110</PlatformToolset>
</PropertyGroup>
Just change the v110 to v90.
Obviously, that is kind of a hack. The v90 option should be there in the project properties. If this doesn't work, you could try reinstalling or repairing the 2008 install.
I am developing a command line application that creates a full Visual Studio 11 solution made of a single VC++ project and that tries to compile it in the end using MSBuild.
The problem I am facing is strange.
If I execute my command line program inside Visual Studio 11 it works; if I instead launch it outside the development environment it throws me the error:
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32\Microsoft.Cpp.Win32.Targets(511,5): error MSB8008: Specified platform toolset (v110) is not installed or invalid. Please make sure that a supported PlatformToolset value is selected. [f:\ABC.vcxproj]
The command I am using is the following:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe f:\snake\W9A30040.vcxproj /property:PlatformToolset=v110;Configuration=Debug /v:quiet
But I have the feeling that PlatformToolset=v110 is ignored and MSBuild use v100 (Visual Studio 2010).
Do you have any suggestions how to tell MSBuild to compile for v110 Platform Toolset?
I ran into the same problem as well with the full release of VS 2012. You can also set the VisualStudioVersion as a property with MSBuild as opposed to dealing with environment variables as mentioned in the accepted answer. For instance:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe .\myproject.vcxproj /p:VisualStudioVersion=11.0
The environment variables approach I'm sure work just as well, I honestly didn't try that as I was trying to stay away from having to modify the environment variables.
Make sure that the top of your .SLN file looks like this:
Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio 2012
When you double-click on the solution file, it's the # Visual Studio 2012 that controls which version of Visual Studio is loaded (and controls the icon displayed in Windows Explorer).
However, when you run MSBuild, it looks at the Format Version 12.00 part.
Confused?
This is confusing, since Visual Studio 2010 is version 10.0 and Visual Studio 2012 is version 11.0 (not 12.0), and using the version 12.0 solution file format causes MSBuild to (implicitly) set VisualStudioVersion to 11.0.
I found a workaround for this issue; could be a problem of Visual Studio 11 Beta that will be resolved before official release.
Anyway, if you are interestedm just set the environment variable "VisualStudioVersion" equal to "11.0" before calling MSBuild.exe.
In batch files
set VisualStudioVersion=11.0
or in VB.NET
Environment.SetEnvironmentVariable("VisualStudioVersion", "11.0")
Starting with Visual Studio 2013, MSBuild is now part of Visual Studio, and the correct path should be $(MSBuildToolsPath) (“C:\Program Files (x86)\MSBuild\12.0\Bin”). If you use msbuild.exe from the .Net framework folder (“C:\Windows\Microsoft.NET\Framework64\v4.0.30319”) it will not able to distinguish the vs2012 and vs2013 versions.
Use the menu based options to do this. From VC++2010 Express:
- Right click on the main file of the project (not the solution itself at the very top of the tree).
- Click General.
- Find Platform Toolset on the right side of the dialog, top half.
- Change from v110 to v100.
- Click OK.
----- Done ------
Microsoft provides a batch file to set all the EnvVars
You find it in the Start Menu under "Microsoft Visual Studio 2012/Visual Studio Tools" or in the Visual Studio folder ("C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools\VsDevCmd.bat")
Is there an Expression Tree Visualizer for VS 2012? Have had a search but have found the VS 2008 popping up all over the place, and the new VS 2012 doesn't have a Visualizers folder in the installation directory. Or, am I missing something that I should be able to switch on?
What you can do is fix the visualizer for vs 2010 so it works in 2012. This is very easy. Just get the source from this project : http://exprtreevisualizer.codeplex.com/ and change the DebuggerVisualizers assembly reference of the ExpressionTreeViewer project to :
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\ReferenceAssemblies\v2.0\Microsoft.VisualStudio.DebuggerVisualizers.dll
So that it works with the newest version of vs2012. After that copy the results to
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Packages\Debugger\Visualizers
and it should work
No but you have DebugView, in debug mode, there's a proxy for the class with the same properties and an added one DebugView. It's text like. Also Mono.Linq.Expressions has a text writer for expressions that makes C# code, check it out.
I seem to make bad *.dll's when this issue re-occurred for me. I started a GitHub repo with the solution. I included a built and the compiled *.dll which can be downloaded by clicking "View Raw" on this file.
Copy this *.dll to your visualizer directory of choice. I use C:\Users[CurrentUser]\Documents\Visual Studio 2013\Visualizers
(Disclaimer: I am the author of the visualizer in question.)
I've written a debugging visualizer for Visual Studio:
I just wanted to know what is inside the Visual C ++ runtime DLLs? What code? Which functions? Just curious about that.
Thanks in advance.
Is contains standard functions, like prinft, exit etc.
You can find the source code for the library in "C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\crt\src" (This is Visual Studio 2008)
The basic dll for Visual Studio 2008 is is msvcrt90.dll
See also this link
The runtime contains code, that is common to/needed in all C++ programs ('think default libraries') and generaly links your code to the OS and it's API.
Code to initialise the app, set up I/O, minimal error reporting/logging, memory management etc ..