- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Steve,
Does Intel have a schedule for requiring users to migrate from MSVS2010? If so, it would be helpful to know so that I can submit a budget request for the upgrade.
Thanks,
David
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Vs2012 seemed an improvement over vs2010 but I have doubts about vs2015. Historically, intel has supported at least 3 visual studios as long as Microsoft does. The free vs2013 seems ok if your organization qualifies.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is not something we have discussed yet, but as Tim says, we typically support three VS versions. We'll support VS2010 through the 2016/16.0 product cycle, but I think it reasonable to expect that it will get dropped for the next major release after that (in the second half of 2016). Note that we will be replacing VS2010 Shell with VS2013 Shell in the 16.0 product.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Last year I upgraded from VS 2010 to 2012, then did the upgrade to VS 2013. I haven't done VS 2015(or next). I usually wait to advance MS VS until after the Intel Parallel Studio XE integration issues sort themselves out. My motto - if it works, don't break it.
I did some collaboration on an Android project last year and my collaborator was constantly updating his system, like the moment any update comes out (daily in some cases). Trying to keep things synchronized between his system and mine, as well as keeping the developing application stable, was difficult to say the least.
So far I am happy with the Parallel Studio XE 2015 on MS VS 2013. The only issue I had with PS 2015, was the base level had integration issues. The update 4 has a quirk (benign when you know about it) in that after you install the update, you must reboot your system. Otherwise launching MS VS 2013 errors out due to environment variables mixups. After reboot it seems to work... excepting for launching the PS command line windows, their paths are a bit goofed up too. Running from the IDE has had no problems (other than some configuration issues relating to building/debugging/running a C# managed app, calling an MS C++ managed dll, calling unmanaged IVF Fortran library or dll. It is all working now, and everything makes sense _after_ you figure out what to do.
Jim Dempsey
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I spent more time than I like yesterday resolving some problems with 2015 update 4 and beta update 1 by uninstalling all possible intel tools following up with special uninst aller. Then a fresh install of update 4 compilers and beta parallel studio against vs2012 13 and 15 went smoothly.
Command line paths aren't entirely correct. Vs2015 cl won't run in an intel compiler window due to conflicts with icl.
ifort and icl with O3 debug set give the message about not using mspdb1xx.dll and dropping back to Z7. This doesn't appear to create a problem in Advisor. I followed posted advice but couldn't stop the message.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Microsoft mainline support for VS 2010 ends in a few weeks time on 7/14/2015 and therefore it wont be supported on Windows 10.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page