Fixed #247 Solution analysis missing project in folders.

You need to have updated your Visual Studio 2019 to at least 16.8.

Fixed #247 Solution analysis missing project in folders.
This bug fix was brought to you by @ElRato, who both reported, debugged and subsequently fixed the bug. Thank you very much for your contribution!

KNOWN ISSUES:

• I am aware that some of you do not get the benefit of the automatic resolving of game binary files. I have yet to be able to reproduce the problem, so I cannot fix it. In the mean time you can get around the issue by setting this folder manually in the Tools|Options|MDK/SE. Check the Game Install Path (Bin64) checkbox and find your Space Engineers installation folder, and the Bin64 folder inside that.

• After upgrading your project, VS might complain that it does not find the MDK analyzer. This is caused by the project not getting properly upgraded. I don't know why the upgrade wizard doesn't get run properly, I don't have this problem myself. Unloading / reloading your project manually, by right-clicking the project node, should force the upgrade wizard to run.

Fixed Repair failing because of Steam file format change

You need to have updated your Visual Studio 2019 to at least 16.8.

Fixed #243 Project Health Report locks VS - caused by Steam changing a file format.

KNOWN ISSUE:

After upgrading your project, VS might complain that it does not find the MDK analyzer. This is caused by the project not getting properly upgraded. I don't know why the upgrade wizard doesn't get run properly, I don't have this problem myself. Unloading / reloading your project manually, by right-clicking the project node, should force the upgrade wizard to run.

Fixed project repair removing Immutable reference

You need to have updated your Visual Studio 2019 to at least 16.8.

Fixed #238 Missing System.Collections.Immutable in MDK.paths.probs on repair prompt.

That is all.

KNOWN ISSUE:

After upgrading your project, VS might complain that it does not find the MDK analyzer. This is caused by the project not getting properly upgraded. I don't know why the upgrade wizard doesn't get run properly, I don't have this problem myself. Unloading / reloading your project manually, by right-clicking the project node, should force the upgrade wizard to run.

Bug fix + VS version requirement lockdown

Unfortunately certain changes have forced me to forego the Visual Studio 2017 support permanently. Visual Studio 2019 (16.8) is now required in order to use MDK. I can only apologize, there's nothing I can do about this.

• Fixed certain characters (like &) in path names breaking the MDK property files.
• An attempt to fix the upgrade reload process... only partially successful. You'll need to restart Visual Studio or run Rebuild several times before it stops complaining.

SCBionicle's Lite Minifier

MDK now requires at least Visual Studio 2017 15.9. If you have Visual Studio 2019, make sure you update to at least 16.8.2 as people have reported problems with earlier versions.

Edit 2021-01-01: There are indicators that 2017 support is now dead. I can do nothing but apologize for this.

Adds a lighter version of the minifying tool which does everything the minifier does, except renaming symbols. Thank you @SCBionicle!

KNOWN ISSUE:

After upgrading your project, VS might complain that it does not find the MDK analyzer. This is caused by the project not getting properly upgraded. I don't know why the upgrade wizard doesn't get run properly, I don't have this problem myself. Unloading / reloading your project manually, by right-clicking the project node, should force the upgrade wizard to run.

jeffgriffin's Minifier Breaking Code Bugfix

MDK now requires at least Visual Studio 2017 15.9

Fixes #207 CodeSimplifier changes access modifiers for unreferenced base classes/interfaces

when the base classes/interfaces are nested in Program and referenced in non-nested types. It's an edge case and rare, but a fix is a fix! Thank you @jeffgriffin!

KNOWN ISSUE:

After upgrading your project, VS might complain that it does not find the MDK analyzer. A Clear\Rebuild should fix that for you. If not, exit Visual Studio, delete the .vs, bin and obj folders and try again. It should work.

Vindicar's Comment Stripping Feature

MDK now requires at least Visual Studio 2017 15.9

#177 @the-vindicar's Comment Stripping Feature

Keep your original source code well documented with comments, but strip them away to save on characters when building the final script for the programmable block.

Thank you Vindicar!

KNOWN ISSUE:

After upgrading your project, VS might complain that it does not find the MDK analyzer. A Clear\Rebuild should fix that for you. If not, exit Visual Studio, delete the .vs, bin and obj folders and try again. It should work.

Vindicar's Comment Stripping Feature

MDK now requires at least Visual Studio 2017 15.9

#177 @the-vindicar's Comment Stripping Feature

Keep your original source code well documented with comments, but strip them away to save on characters when building the final script for the programmable block.

Thank you Vindicar!

KNOWN ISSUE:

After upgrading your project, VS might complain that it does not find the MDK analyzer. A Clear\Rebuild should fix that for you. If not, exit Visual Studio, delete the .vs, bin and obj folders and try again. It should work.

Bug Fix Release

Fixes #172 (Thank you @lukekaalim)

KNOWN ISSUE:

After upgrading your project, VS might complain that it does not find the MDK analyzer. A Clear\Rebuild should fix that for you. If not, exit Visual Studio, delete the .vs, bin and obj folders and try again. It should work.

Attempt to fix loading issues

MDK now requires at least Visual Studio 2017 15.9

Removed debug code that for some reason crashed runtime. Shouldn't crash even if it was there though. Did I somehow manage to release a debug version?
Added MDK dev console and relevant output
Changed how solution load status is detected (attempt to fix #141 and #156)