I wanted to know if anybody had the experience of configuring this : http://www.microsoft.com/en-us/download/confirmation.aspx?id=41151
into visual studio 2010 ?
I have only Windows Vista on some of my machines; and I'd like to code using a 2012 or 2013 compiler. I know visual studio is greatly configurable and can plug various compilers (like sony for PS Vita is providing a configuration for gcc based compiler in visual studio).
VS 2012 and 2013 express cannot be installed on Vista. But I see no reason why the compiler; a purely command line tool, wouldn't work on Vista. (because it wouldn't dare to need that darn K32GetModuleInformation thingie. I bet MS called this function for purely phony purposes of forcing people to upgrade their OS)
thanks !
ps : of course a trick to make vs 2013 express (for desktop) installable on vista would also be appreciated.
Related
I have a project created on Visual Studio 2010. When I try to run the project on Visual Studio 2015 Community edition I get the error below,
Severity Code Description Project File Line
Error MSB8020 The build tools for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please install Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution". graphics C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Platform.targets 55
And when I tried to build it with Visual Studio 2015 Build Tools I encountered about 1500+ errors.
Is there any way to make the project work?
If you can't install VS2010, Windows SDK for Windows 7 contains needed compiler tools (v100), you may actually skip installing the SDK itself and install only the compiler tools, headers and libs. Please note, that the compiler included in Windows SDK is the same that VS2010 has, but VS2010 SP1 has a bit newer compiler. If you need that, you'll also need to install Microsoft Visual C++ 2010 Service Pack 1 Compiler Update for the Windows SDK 7.1. But be aware, that if you install these, you may have issues later if you decide to install VS2010, there are bugs in installer that requires you to install components in strict order. Also, if your code uses MFC or ATL you must install VS2010, installing Windows SDK will not be enough.
You either install VS 2010 and build your project, or better yet you upgrade your projects. The VS 2015 custom install options will let you install the v120 Platform Toolset, but not the v110 or v100 Platform Toolsets.
One major change in VS 2015 is that the C++ tools (i.e. v140) are not installed by the Typical installation option. See the Visual C++ Team Blog.
Keep in mind that Visual C++ 2010 used the C++0x Draft Standard, and Visual C++ 2015 meets the C++11 Standard with the exception of Expression SFINAE (which is partly there in Update 1), so quite a bit has changed in the intervening years including some breaking changes. Since you are jumping three major releases at once--and about 10 minor updates--, it can be a bit overwhelming especially working through all the new warnings.
Another thing to keep in mind is that Visual C++ 2010 used the Windows 7.1 SDK, while Visual C++ 2012 or later use the Windows 8.x SDK. There's been a lot of change there too particularly for DirectX development. It's particularly important for Windows desktop apps that you set the _WIN32_WINNT preprocessor define for your target platform as the Windows 8.x SDK does not default to the 'oldest supported platform' like earlier Windows SDKs did. See Using the Windows Headers
VS 2010 and the v100 toolset supports targeting Windows XP and Windows Server 2003. The v140 toolset does not support targeting Windows XP / Server 2003. You have to use v140_xp Platform Toolset instead. See this post for some notes as this means you are again using the Windows 7.1 SDK rather than the Windows 8.x SDK with the _xp toolsets.
See Breaking Changes in Visual C++ 2012, Breaking Changes in Visual C++ 2013, and Breaking Changes in Visual C++ 2015.
See also Support For C++11/14/17 Features (Modern C++), and Where is the DirectX SDK?.
If you need to build the code both with VS 2010 and with VS 2015, then you should create two projects/solution files, one for each. You may also want to read this article for some notes on writing code that can build with multiple Visual C++ toolsets, which again is particularly challenging due to the Windows SDK changes.
VS 2015 supports targeting Windows Vista SP2, Windows 7 SP1, Windows 8.0, Windows 8.1, Windows 10, and optionally Windows XP SP3. It does not support targeting Windows Vista RTM, Windows Vista SP1, or Windows 7 RTM.
So I am in college and by this fact I have an opportunity to have a Resharper for free. Currently I write in C++, so I downloaded a Resharper for C++ and I've tried to install it. I've got three different VS versions:
Visual Studio 2015 Enterprise
Visual Studio 2013 for Windows Desktop
Visual Studio 2012 for Windows Desktop
When I try to install Resharper I only see the option to install it to VS 2015. Is there no option to install it on 2012/2013 version? (I got Desktop version, cuz they are a lot of lighter and faster on my laptop)
Assuming that 2012 and 2013 versions are the Express editions (which is implied from the names), then ReSharper won't work as these versions don't support extensions and plugins.
You need the full versions of Visual Studio to get this functionality.
As an aside, I'm not sure why you need to install three versions of Visual Studio. Won't the latest version do?
Which version of windows XP does Visual Studio 2012 supports.
[Edit: Which version does VS12 supports compiling to]
I found this article:
http://blogs.msdn.com/b/vcblog/archive/2012/10/08/windows-xp-targeting-with-c-in-visual-studio-2012.aspx
That states that it supports XP SP3. But I didn't find any information for VS12 update 4.
Also, If the code I compile using VS12 doesn't crush on XP SP2 and seems to work.
Is it safe to use it? why not?
Thanks
It's correct, Visual Studio 2012 can compile binaries compatible with Windows XP SP3.
You need to install the Platform Toolset v110_xp and select it in the general configuration properties of your project.
If "safe" means that it works the answere is yes. We have 12.000 installations of our software compiled with Visual Studio 2012 (and recently Visual Studio 2013) perfectly working on Windows XP SP3.
The only big problem is run time debugging: you can't install Visual Studio 2012 on Windows XP so it could be a problem to find bugs that accidentally happens only on Windows XP.
Do you know software support assist for Visual C++ 2010 Express ?, as Visual Assist X for Visual Studio
Installing any plugin requires running the IDE in Integrated Mode (rather than Isolated Mode), which means you'll need a full version of Visual Studio. The express editions simply don't have the feature.
Couple of options to get a version capable of Integrated Mode:
If you are a university student, you can download a full version of Visual Studio from MSDNAA.
If you are a student where MSDNAA is not available, you can still get the full copy from DreanSpark if you can show proof of being a student. (A report card should suffice)
You could purchase the full version of Visual Studio -- I'm assuming this is probably cost prohibitive.
How do I use the profiler in Visual Studio 2008?
I know theres a build option in Config Properties -> Linker -> Advanced -> Profile (/PROFILE), however I can't find anything about actauly using it, only articles I was able to find appear to only apply to older versions of Visual Studio (eg most say to goto Build->Profile to bring up the profile dialog box, yet in 2008 there is no such menu item).
Is this because Visual Studio 2008 does not include a profiler, and if it does where is it and where is the documentation for it?
Microsoft has released stand-alone Profiler for VS 2008 here
The profiler is only available in the Team System editions of Visual Studio 2008. The last version that I used that included a profiler was Visual C++ 6.0.
For Visual Studio 2005, you could try Compuware DevPartner Performance Analysis Community Edition.
There was also a list of .NET profilers in the What Are Some Good .NET Profilers question.
As I understood from reading a few sites, when you use VS 2008 stand alone profiler to create .vsp files, you will need either VS2008 Premium or Ultimate to view .vsp files.
By the way, I installed VS2012 Release candidate which is available for free (trial version?) and I can use its profiling engine.