Jump to content
  • entries
    943
  • comments
    5,899
  • views
    923,507

Visual Studio 2017: Not Ready


Josh

2,853 views

 Share

blog-0663471001481726880.png

A release candidate for Visual Studio 2017 was released in November. I took a chance that the final release would be out in December, but it isn't here yet. Releasing Leadwerks 4.2 built with VC 2017 could possibly cause the program to not run on some computers, because the Visual Studio 2017 redistributable is not out yet, and there is no option yet to make this part of the installation on Steam.

 

Because of this, I am going to release Leadwerks 4.2 for use with Visual Studio 2015, and upgrade to 2017 when the final release is available.

 

If you have a VS 2017 project, it is easy to downgrade it. Open the solution file and change the VS version to 14:

VisualStudioVersion = 14.0.0.0

 

Open the vcxproj file and change the tools version from 15 to 14:

ToolsVersion="14.0"

 

Find and replace all instances of "v141" with "v140", save the file, and you're done.

 

You might even be able to continue using VS 2017 with no changes at all.

 

If you want to stick with VS 2013, it might be possible to just install the 2015 build tools, but I don't know for sure. If you try it, be sure to let us know your results.

  • Upvote 1
 Share

3 Comments


Recommended Comments

I think it is more an issue of the debug build, but I am not completely sure. For the next three months or so, I would play it safe and stick with 2015, if it was me. Which is basically what I'm doing.

Link to comment
Guest
Add a comment...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...