![]() Nuget packages have no knowledge of VS versions (you don't even need VS for Nuget) so I'm really curious as to the issue.We use a “Visual Studio Offline Layout” to deploy VS 16.6 to both developers and buildservers with mixed internet connections (offline / proxy / direct). Personally I would resolve whatever issue you're having with upgrading to the latest minor release. ![]() I'm also going to assume that it requires that you had cached the installer files when you originally ran the setup program but I'm just guessing here. This needs to be done on a machine that has the version you want though as otherwise it isn't available. The recommended approach is to create an offline installer as documented here. What error do you get when you try to install Pro from the installer? I suspect it is that it cannot find it anymore. Additionally if you run the VS installer it'll auto-update to the latest version anyway. So that is most likely why you're having a difficult time finding it. Therefore you're running an unsupported version of VS anyway. Interestingly enough 16.8 isn't listed as a supported version because it wasn't an LTS release. ![]() There should be nothing that prevents you from upgrading VS versions. I think the "bug" is that you cannot upgrade VS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |