This project is read-only.
12
Vote

can we get a vs2017 installer?

description

Hi,

could you make a vs2017rc / vs2017 installer please :) ?

comments

mklemarczyk wrote Jan 14, 2017 at 4:14 PM

Sure, if you are interested in that.

wrote Jan 14, 2017 at 4:18 PM

wrote Jan 14, 2017 at 4:18 PM

DarkPrisma wrote Jan 14, 2017 at 5:34 PM

yes :D thank u!

wrote Jan 19, 2017 at 8:29 AM

wrote Feb 18, 2017 at 7:19 AM

jsmars wrote Feb 18, 2017 at 7:20 AM

Yes please!

jsmars wrote Feb 28, 2017 at 7:28 AM

Any progress on this?

As described in my thread on Reddit. It's possible to come as far as to build and run XNA projects by modifying the installer and moving some files. But we've run into an error we haven't been able to solve for building content projects:

Any idea how to get past this?
Error loading pipeline assembly "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETFramework\v4.0\Microsoft.Build.Framework.dll".

PowerUser123 wrote Mar 8, 2017 at 5:17 PM

Bump, what's the ETA of the new extension?

wrote Mar 8, 2017 at 7:49 PM

kainazzzo wrote Mar 8, 2017 at 7:55 PM

I would like this as well!

wrote Mar 9, 2017 at 12:51 PM

wrote Mar 9, 2017 at 7:31 PM

roytri wrote Mar 10, 2017 at 12:17 PM

I've solved the Error Loading Pipeline Assembly problem. See this gist: https://gist.github.com/roy-t/2f089414078bf7218350e8c847951255

wrote Mar 10, 2017 at 12:18 PM

mklemarczyk wrote Mar 10, 2017 at 9:25 PM

Hi All,

New release will be available for public on March 18th, 2017.

Best regards,
Maciek

wrote Mar 19, 2017 at 7:45 AM

kainazzzo wrote Mar 20, 2017 at 12:42 PM

Thank you!

PowerUser123 wrote Mar 20, 2017 at 3:14 PM

Wait, I can't see a download link to the new extension.... It was supposed to release 2 days ago. What's delaying it so much? Bugs?

DarkPrisma wrote Mar 22, 2017 at 1:22 PM

whats wrong ? :) please tell us if we can help...

PowerUser123 wrote Mar 22, 2017 at 2:13 PM

Yeah I'm forced to work with VS 2015, if there's anything we can do to speed up the release we'd be glad to help. If you can't finish development, let us download the unfinished project and maybe with the help of the folks on that Reddit thread we could find a fix.

wrote Mar 22, 2017 at 2:28 PM

mklemarczyk wrote Mar 26, 2017 at 10:33 AM

There are some changes that Microsoft done in Visual Studio.
Some aliases now point to other directories that stop extension from working properly.

PowerUser123 wrote Mar 26, 2017 at 3:49 PM

Can you figure it out? I see you've uploaded an alpha, but it doesn't work...

wrote Mar 28, 2017 at 7:59 AM

wrote Mar 30, 2017 at 5:57 PM

Darkside wrote Mar 30, 2017 at 5:59 PM

I take it the current issue now is the following error on build?
"Your installation of XNA Game Studio does not support this project (XNA Platform = 'Windows', XNA Framework Version = 'v4.0')."


Any ideas as to the cause?

PowerUser123 wrote May 1, 2017 at 10:48 AM

Bump. Still waiting for the new installer.

mklemarczyk wrote May 1, 2017 at 2:28 PM

The project is over since codeplex will be closed and repo is locked in read-only status.

kainazzzo wrote May 1, 2017 at 3:51 PM

That is not true. First of all, the project need not be tied directly to codeplex's status. Furthermore, from the blog post detailing Codeplex's shutdown:

The shutdown plan
So, it’s time to say goodbye to CodePlex.  As of this post, we’ve disabled the ability to create new CodePlex projects.  In October, we’ll set CodePlex to read-only, before shutting it down completely on December 15th, 2017.

We still have several months before this project is read only.

PowerUser123 wrote May 2, 2017 at 2:11 PM

So you haven't done anything towards fixing the installer? During all of April?

DarkPrisma wrote May 8, 2017 at 11:57 AM

so, we can't expect any updates to that issue? very sad :(

VicViper wrote May 18, 2017 at 5:16 PM

mklemarczyk, could you confirm if you're still working on fixing the issue?

We're still waiting fo a fix, because right now, we have changed our dev environment with virtual machines, one with Vs2015 to use XNA and Vs2017 with new stuff... and it is extremely to work like that.

We were expecting this so we can get rid of the virtual machines and work only with VS2017.

I don't intend to add more pressure on you... I am aware there's extra difficulties with the new MSBuild and Microsoft was not very helpful on that...