1,202 questions
Use the command line to download an offline installer the download and then install option in the ui will only work that computer
vs_enterprise.exe --layout c:\localVScache --lang en-US
Visual Studio 2019: Install on computer without internet connectivity
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 25%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
Brian Schmidt
1
Reputation point
We need to install a copy of Visual Studio 2019 on a computer without an internet connection, it must be entirely installed by file(s) we physically place on it.
MSFT no longer provides ISO images and the instructions for creating an offline installation (https://learn.microsoft.com/en-us/visualstudio/install/create-an-offline-installation-of-visual-studio?view=vs-2022) clearly state "Do not use the Download all, then install feature to create a local cache that you intend to transfer to another computer. It's not designed to work that way."
Given this information, how can we do this? We would very much dislike to use another IDE but do not see how we can get this installed on that network.
Developer technologies Visual Studio Setup
Developer technologies Visual Studio Other
5,451 questions
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 94%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHM%3C/text%3E%3C/svg%3E)
Harsha M S 1 Reputation point2022-03-08T12:55:39.68+00:00 Still facing same issues Microsoft.VisualStudio.DebuggerClient.Concord.Remote.Resources and Microsoft.VisualStudio.LiveShare.VSCore when we created offline files.
Is there a workaround for this?
Sign in to comment
2 answers
Sort by: Most helpful
-
Ken Tucker 5,861 Reputation points2022-01-28T11:32:14.903+00:00 -
Brian Schmidt 1 Reputation point
2022-02-01T20:03:15.99+00:00 Thank you it took a while to get the files copied so was just able to run it.
I had downloaded VS2019 Professional from MSDN and so ran "vs_professional__840991a81e7d4596b1653605bff28232.exe --layout c:\localVScache --lang en-US".
This looked like it created the files I needed, however, when I took them to the PC without a network connection and ran vs_setup.exe an admin:
- The install stopped on two files with very long file names. I selected Continue. Then the set up failed saying it could not reach the internet and “Couldn’t download Microsoft.VisualStudio.Branding.Enterprise", I found this file among the files that I had brought over and copied it to a location where it looks as though it was able to be found. So I think this part is OK.
- Latter the install failed completely saying it could not find Microsoft.VisualStudio.LiveShare.VSCore, version=2.0.882.1 and Microsoft.VisualStudio.DebuggerClient.Concord.Remote.Resources, version=16.1132104.304.
It's close I think but still not able to install it. Is there maybe another switch I should be using?
Sign in to comment -
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 91%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
John 1 Reputation point2022-05-13T21:16:19.71+00:00 When creating a Visual Studio 2022 offline installer I ran into a similar problem with "Microsoft.VisualStudio.DebuggerClient.Concord.Remote.Resources,version=17.2.32414.121,chip=x64,language=en-US,productarch=neutral"
Upon closer inspection of the layout, I found that the component's directory name had become mangled. I don't know at what step in the process this happened, but I corrected the directory name (copied the full package name listed in the error log and renamed the directory), retried the installation, and the installation completed with no problems.