The latest version of Box2D is made for VS2013, while my currently version of VS is 2015, while it should not cause any trouble on simpler code...It does.
I've been dealing with a lot of errors (I fixed most of them) but still it doesn't seem to work at its potential.
While VS2015 is not a necessity for me I would simply downgrade it, but I'm concerned if that is going to do any good on Box2D.
My question is :
Should I deal with Box2D in VS2015 or should I downgrade that to 2013.
While I wasn't 100% sure, downgrading really fixed all the errors I had, so I would recommend if someone has some minor errors which include :
1.Warnings, lots of them
2.Any possible error which isn't answered anywhere
3.Exceptions
To downgrade to the specified version
Related
I brought up a new VS2017 dev environment at work yesterday, which means I got the recently released version 15.3. I'm getting an internal compiler error on a VC++ project that nobody else in the organization is getting; everyone else is still on 15.2. To test my theory that the 15.3 update may have broken something, I want to install VS2017 15.2 (or even 15.1 or 15.0). But I can't figure out how to do that. When I run the 15.0 or 15.1 bootstrapper, it still tries to install 15.3.
I've already gone over this guide for creating offline installations but it doesn't say anything about getting an older release. I found a guide here that shows how to use a specific release with VS2015, but I can't find anything for VS2017.
My work gave me an MSDN account (Visual Studio Professional), which offers older bootstrapper downloads, but does not offer full offline installation downloads for older releases.
How do I install VS2017 15.2 (or 15.1, or 15.0) when 15.3 has already been deployed by Microsoft?
There is support for downloading a prior version, but evidently you have to contact support for the link. None of the links on any of the pages I could find within the VisualStudio.com site referenced it.
Installing an earlier release of Visual Studio 2017
Be sure to take the time to read the "[no]support policy" regarding "earlier" releases. Essentially, the day they released version 15.4, version 15.3.5 was no longer supported.
On another note, I have noticed many people seem to respond (here and on other similar postings) along the lines of "Why on earth would you want to reinstall the same version you were working with instead of the latest release?". Note that I am para-phrasing that to clarify the sentiments commonly expressed.
The reason is because TEAMS of developers need to be on the SAME version of the tool set. They have deadlines and cannot afford to drop everything and switch everybody to a new version of the tools that may or may not work correctly for them. Even if the developers were willing to take that hit to their productivity, usually their managers are not. This is why taking away the option to install the previous version the very same day you make a new release available is an unacceptable practice for Enterprise or Professional grade development software.
Another common reason is that when bugs have to be fixed in software, you often need to use the same, or very close to same, version of the tools to rebuild it after fixing the bug. The costs of regression testing after forcing a non-trivial upgrade on an entire software product or suite is unacceptable to most organizations. Upgrading may not even be an option due to contractual obligations.
It seems that based on this article that Microsoft do not offer a mechanism to download any version of Visual Studio 2017.
The https://my.visualstudio.com site offers bootstrap downloaders for 15.0 and 15.3 only. Intermediate versions such as 15.1 and 15.2 are not available as of September 2017.
I have a modest sized engineering team that would quite like to stay with 15.2 even for new starts and this is quite frustrating as we didn't capture an offline install of anything other than 15.0!
Apparently its possible to install a older version in parallel to a newer one. I just downloaded 15.6.7 from https://learn.microsoft.com/en-us/visualstudio/productinfo/installing-an-earlier-release-of-vs2017 and started the install - it didnt touch my existing installation 15.9.19
But the probably better solution is just to install the toolset which is available separately for each VC2017 release. See this intersting article:
https://devblogs.microsoft.com/cppblog/side-by-side-minor-version-msvc-toolsets-in-visual-studio-2017/
I'm getting the attached error after having re-installed my computer and having simply re-installed VS2017.
Does anybody know how to fix this problem?
I don't remember anymore what I did to include this header in the previous VS version.
My best guess would be that I downloaded a platform SDK, but I have no idea which one I should download using VS2017.
Thank you very much for an advice.
Edit: I already have this SDK installed: https://developer.microsoft.com/en-US/windows/downloads/windows-10-sdk
It doesn't work anyways.
I selected Project->Properties->Windows SDK-Version->Default or Inherit from Standard.
And it worked.
It's now "7.0" as it had been before, but for some reason it works now.
Thanks to myself.
Also, I had to edit the Platform Toolset when I wanted to build the Release.
Here is a screenshot:
I'm doing a project with a couple of other guys who have vs10, will it hurt if just I upgrade to vs12. Will it hurt when we all check in on svn? Will everything still be compatible as far as wpf, mvc, etc.. goes. Should I be aware of anything about the new visual studio 2012?
I personally would keep a similar environment to everyone else working on the project - either all go 2012 or all stay 2010.
Not to say that there are or are not known issues with working between the two environments, but why introduce possible problems when you're going to work with the lowest possible common denominator anyways?
Using VS2012 and VS2010 seems to work flawlessly, so far. I installed it a month ago when it became available on MSDN. I've worked on several problems since then without any compatibility issues. Rather worryingly though, we've come across an issue where a linq to entities query works fine on a machine without .net 4.5, but fails on a machine with .net 4.5, despite the project targeting .net 4.0. A colleague is looking at this at the moment, so I don't have any more details
I currently have Visual Studio v2003, v2005, v2008 installed on my system. Things work fine...no issues.
I now have to install Visual Studio 2010 on my system and just wanted to know if anyone has a setup like mine or knows if there are any potential issues with so many versions existing on a system.
Really don't have a choice to remove older versions as we have a lot of legacy products written in these old versions and we are not upgrading them to new versions, only doing bug fixes on them.
Any ideas?
Thanks!
VS2010 supports targeting on multiple versions of .NET Framework (i.e. 2.0 or later), which mean it is designed to support the projects that were built with VS2005/VS2008 so-called backward-compatibility.
So I think no conflict here between these versions,
I've found a nice Myths and facts about VS 2005/2008/2010, check out this link here: http://msdn.microsoft.com/en-gb/ee679805.aspx
It should work.
I have vs2003, vs2008 and vs2010 installed and I see no issue (but vs2010 is not yet used for production code).
M.
All these versions of Visual Studio are independent.
You should have no problem (other than lack of disk space!) installing VS2010 as well.
Just make sure you install the service pack as well.
They cohabitate fine, I have a similar setup myself.
You should at least push for migrating away from 2003 and 2005 though, they use some pretty old technology, and pretty much everyone these days has .net 3.5 on their systems.
If you are able to use VS 2010 I would highly recommend you do for all new projects - even if you have to target an earlier version of .NET framework.
Keep the old versions of VS installed only for maintenance of projects that cannot be migrated to VS 2010 version.
By the way, the migration to VS 2010 is often very trivial and well worth an hour or two of effort!
I used to install betas freely and learned the hard way that I best only do that using a disposable environment.
What is your perception of the safetey of installing the Release Candidate version? Is it likely that when I go to install the final version that I will be faced with having to do ugly manual steps to get rid of it just so I can install the actual release version?
I just un-installed beta 2 from a machine I use to code on (not my main work dev PC though) fairly frequently. The uninstaller does a very good job of tidying up and only left behind the Visual Studio Tools for Office runtime. I then installed the RC and everything went fine and nothing seems to have broken. Based on the beta 2 uninstaller behaviour I expect the RC should uninstall nicely when RTM time comes around .
That said, the usual caveats that apply to all pre-release software still apply here. If the machine you're thinking of installing onto is mission critical then don't take the risk, use a VM or a machine you can afford the time to rebuild instead.