Microsoft Killed the Deploy Function

Yeah... this isn't actually an update...

If you haven't updated to Visual Studio 2022 17.9 yet, and you're using MDK, don't. They broke the Deploy function in a way I can't fix. I have an alpha part of MDK2 availble as a workaround, see #308, but it does not have a minifier yet.

I am working on MDK2 but it's slow going. It is coming along though.

I will be moving away from a pure Visual Studio addon. Do not worry though, it will still work just fine for Visual Studio, it will just be a little different. And also, if you have a different favorite editor/ide, you'll be happy to know you can probably use MDK2 with that too, as it will be editor agnostic.

Go to the MDK2 Repository to get started with MDK2 instead.

Eventually there will be better documentation... 😅

Compatibility Release

Sorry! Sorry! Sorry! Keen finally did what they said they were gonna do and killed the -plugin argument... I should have paid attention but I didn't. So whitelist didn't update so I thought it didn't change 😳

Fixed it now...

Visual Studio 2022 community edition is free. It can be installed side-by-side with your existing VS'19 installation if needed. If you already have VS'22 installed, make sure it's updated to at least 17.5.4.
https://visualstudio.microsoft.com/vs/community/

NOTE The usual Visual Studio shenanigans apparently is still alive and well.
You might have to clear\rebuild and restart Visual Studio several times before whatever caches it's messing about with gets fixed... You'll get complaints about the analyzer, the MDK.Utilities assemblies, all sorts of BS before it realizes that "hey, everything is actually in order." 🙄

Pesky Update Dialog!

• Apparently, a 3rd-party system I used to generate some information has died, causing bad version info to get into the addin, causing a confused update-checker. Fixed that.
• Removed the manual update of the whitelist cache, as it crashes now and will stop working permanently anyway since Keen is changing their plugin policy. Besides, I tend to update MDK with the new whitelists anyway.

Visual Studio 2022 community edition is free. It can be installed side-by-side with your existing VS'19 installation if needed. If you already have VS'22 installed, make sure it's updated to at least 17.5.4.
https://visualstudio.microsoft.com/vs/community/

NOTE The usual Visual Studio shenanigans apparently is still alive and well.
You might have to clear\rebuild and restart Visual Studio several times before whatever caches it's messing about with gets fixed... You'll get complaints about the analyzer, the MDK.Utilities assemblies, all sorts of BS before it realizes that "hey, everything is actually in order." 🙄

Migration to Visual Studio 2022

Visual Studio 2022 supported, finally!

Microsoft has made enough updates and changes for me to finally be able to move MDK from 2019 to 2022!

No, this is not the infamous MDK2, but the good ol' MDK migrated to the new '22 form.

Visual Studio 2022 community edition is free. It can be installed side-by-side with your existing VS'19 installation if needed. If you already have VS'22 installed, make sure it's updated to at least 17.5.4.
https://visualstudio.microsoft.com/vs/community/

Unfortunately I will not be able to support Visual Studio 2019 going forward. I am very sorry for this, but I do not have the capacity to maintain both projects.

NOTE The usual Visual Studio shenanigans apparently is still alive and well.
You might have to clear\rebuild and restart Visual Studio several times before whatever caches it's messing about with gets fixed... You'll get complaints about the analyzer, the MDK.Utilities assemblies, all sorts of BS before it realizes that "hey, everything is actually in order." 🙄

Crash on deploy/copy to clipboard

• Attempt to fix a crash happening to some people when deploying then clicking copy to clipboard.

Visual Studio 2022 community edition is free. It can be installed side-by-side with your existing VS'19 installation if needed. If you already have VS'22 installed, make sure it's updated to at least 17.5.4.
https://visualstudio.microsoft.com/vs/community/

This is a prerelease. Please test it (let me know if you do so I can keep track) and make issues marked VS'22 if problems are found. If you just want to do your job, consider just using the latest release for VS'19 for now... but if you're willing to help me test it would be highly appreciated!

Once this hits public release, the old version for VS'19 will be dropped. I am very sorry for this, but I do not have the capacity to maintain both projects.

NOTE The usual Visual Studio shenanigans apparently is still alive and well.
You might have to clear\rebuild and restart Visual Studio several times before whatever caches it's messing about with gets fixed... You'll get complaints about the analyzer, the MDK.Utilities assemblies, all sorts of BS before it realizes that "hey, everything is actually in order." 🙄

(VS'22) Attempt to fix startup issues

• Fixed several 3rd party assembly references causing problems.
• Improved the upgrade tool to also auto-upgrade the project targeting to 4.8.

Visual Studio 2022 community edition is free. It can be installed side-by-side with your existing VS'19 installation if needed. If you already have VS'22 installed, make sure it's updated to at least 17.5.4.
https://visualstudio.microsoft.com/vs/community/

This is a prerelease. Please test it (let me know if you do so I can keep track) and make issues marked VS'22 if problems are found. If you just want to do your job, consider just using the latest release for VS'19 for now... but if you're willing to help me test it would be highly appreciated!

Once this hits public release, the old version for VS'19 will be dropped. I am very sorry for this, but I do not have the capacity to maintain both projects.

NOTE The usual Visual Studio shenanigans apparently is still alive and well.
You might have to clear\rebuild and restart Visual Studio several times before whatever caches it's messing about with gets fixed... You'll get complaints about the analyzer, the MDK.Utilities assemblies, all sorts of BS before it realizes that "hey, everything is actually in order." 🙄

Visual Studio 2022 support (dropping '19 support, sorry)

Visual Studio 2022 supported, finally!

Microsoft has made enough updates and changes for me to finally be able to move MDK from 2019 to 2022!

No, this is not the infamous MDK2, but the good ol' MDK migrated to the new '22 form.

Visual Studio 2022 community edition is free. It can be installed side-by-side with your existing VS'19 installation if needed. If you already have VS'22 installed, make sure it's updated to at least 17.5.4.
https://visualstudio.microsoft.com/vs/community/

This is a prerelease. Please test it (let me know if you do so I can keep track) and make issues marked VS'22 if problems are found.

Once this hits public release, the old version for VS'19 will be dropped. I am very sorry for this, but I do not have the capacity to maintain both projects.

NOTE The usual Visual Studio shenanigans apparently is still alive and well.
You might have to clear\rebuild and restart Visual Studio several times before whatever caches it's messing about with gets fixed... You'll get complaints about the analyzer, the MDK.Utilities assemblies, all sorts of BS before it realizes that "hey, everything is actually in order." 🙄

Bad Whitelist Cache...

Make sure your Visual Studio 2019 is up to date.

Ooops. Somehow the whitelist cache never got updated on the previous release. Sorry about that.

OBS!!! You will need to install the .NET 4.8 targeting pack if you haven't already.

See https://github.com/malware-dev/MDK-SE/wiki/Getting-Started-with-MDK#step-1

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.

Automation Update + .NET 4.8

Make sure your Visual Studio 2019 is up to date.

Finally updated the templates to use .NET 4.8 rather than 4.6.1.

OBS!!! You will need to install the .NET 4.8 targeting pack if you haven't already.

See https://github.com/malware-dev/MDK-SE/wiki/Getting-Started-with-MDK#step-1

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 #247 Solution analysis missing project in folders. (revised)

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!

Revision: Some project configurations resulted in a NullReferenceException.

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.