Jacques Eloff

The 2.2.2 build was a rebuild of 2.2.1. There was a bug in the 2.2.1 release that contained a security fix. The AssemblyFileVersion properties on the DLL were invalid. This...

@OzBob I'll see if we can find anything. Also, if you want to update from 2.1.0 I recommend the 2.2.3 package. 2.2.2 had a problem with the AssemblyFileVersion (my previous...

That is certainly possible, or package dependencies might have been updated, e.g. when a newer version of EF shipped. The issues I listed are the only ones I could find...

Thank you, this will be really helpful for enterprise customers

Thank you for the PATH writeup @richlander

Are you planning on adding the release-type to older releases.json files, e.g. 1.0 or 2.2? If not, what should be the default value when reading these files for the property?...

> I updated all the release objects in `release-index.json`. I didn't update the old `release.json` files in absence of a reason to do so. If you have a scenario where...

No, at the moment you need to get an official build once your SDK changes flow to installer. This is another good example where merging the repos has real benefits

> > No, at the moment you need to get an official build once your SDK changes flow to installer. This is another good example where merging the repos has...

Did you run the full installer and then install over the contents in Program Files using dotnet-install.ps1? If so, that would mark files as user modified so when trying to...