This project is read-only.

Support for Visual Studio 2017?

Topics: Suggestion
Mar 7 at 4:46 PM
Will this project be updated to support Visual Studio 2017? It is officially released as of today:

http://www.zdnet.com/article/microsofts-visual-studio-2017-is-now-generally-available/
Mar 7 at 4:49 PM
Yes please!
Mar 8 at 5:17 PM
I'm looking forward to this as well.
Mar 10 at 9:29 PM
As was mentioned in issue 14039, it will be released on Match 18th, 2017.
Mar 17 at 9:47 AM
Thank you for all your work.

Is there anything we can accomplish beforehand to prepare for the new release?

My situation: I'm working overseas on a temporary development machine. Had an extended trial version of VS2017 Enterprise which worked flawlessly with the current version of XNA 4.0 Refresh. The trial was to expire so I installed VS2017 Community. Now all of my XNA projects are incompatible. Ran through the steps to do both repairs and fresh installs of XNA 4.0 Refresh to no avail. That's when I saw a new release is imminent.

I'm wincing because I have to go a day without XNA development on this machine. <g>
Mar 19 at 8:40 AM
Installed version 4.0.5 and Visual Studio 2017 Community is still resulting in a migration report stating my XNA solution is incompatible.

First things first, is XNA proven to be supported with VS2017 Community? Google has no detailed results, yet.
Mar 19 at 10:26 AM
v4.0.5 Is incompatible with VS 2017 because it uses the old (and already unsupported) VSIX standard. BTW it's 19th of March already and still no download for VS 2017?
Mar 23 at 3:10 AM
Mar 27 at 8:52 PM
When's the new ETA for 2017 support?
Mar 30 at 5:53 PM
Tried the new VS2017 installed, great work BTW

Can now open XNA projects but sadly can't build / run them. VS2017 simply reports

"Your installation of XNA Game Studio does not support this project (XNA Platform = 'Windows', XNA Framework Version = 'v4.0')"

So it's not detecting the XNA build runtimes for some reason? (all project types / templates work!! though)
Mar 30 at 6:31 PM
We already resolved that problem. Microsoft changed MSBuild directory.

Solution for that problem will be released this week.

Currently we are facing problem with error on local Microsoft.Build.Framework.dll file.
https://github.com/Microsoft/msbuild/issues/1831
Apr 1 at 8:42 AM
Right, thanks for the update. Although, looking at that issue, I thought Roy had a solution, or is it not working?
May 11 at 3:57 PM
mklemarczyk wrote:
We already resolved that problem. Microsoft changed MSBuild directory.

Solution for that problem will be released this week.

Currently we are facing problem with error on local Microsoft.Build.Framework.dll file.
https://github.com/Microsoft/msbuild/issues/1831
Hi @mklemarczyk - Any update on the VS2017 side?
Jun 8 at 6:56 PM
Thanks to Roy Triesscheijn (@roytries http://roy-t.nl), there is a manual work around for getting MSXNA to work under Vs2017. Looking at it, not sure it can be automated sadly.

Details here:
https://gist.github.com/roy-t/2f089414078bf7218350e8c847951255