Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,6 @@ Here are some common local layout creation examples. More examples can be found
vs_enterprise.exe --layout c:\localVSlayout
```


::: moniker range=">=vs-2022"

> [!NOTE]
Expand Down Expand Up @@ -87,7 +86,6 @@ When you install Visual Studio from a local layout, the Visual Studio Installer

For example, if you created a local installation layout with the following command:


::: moniker range=">=vs-2022"

```shell
Expand All @@ -102,6 +100,11 @@ c:\localVSlayout\vs_enterprise.exe --noWeb --add Microsoft.VisualStudio.Workload

::: moniker-end

> [!IMPORTANT]
> When Visual Studio is installed from a local layout, the installer records the layout path in the `C:\ProgramData\Microsoft\VisualStudio\Packages\_Instances\<InstanceID>\state.json` file.
> Future Updates or component additions expect the layout to remain at the same path.
> If the local layout is moved to a different location, the installer may not be able to find the required packages.

> [!IMPORTANT]
> If you're using Visual Studio Community, you might be prompted to sign in within 30 days of installation, but it won't impact your ability to use the product.

Expand Down
4 changes: 4 additions & 0 deletions docs/install/deploy-a-layout-onto-a-client-machine.md
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,10 @@ You need to make sure that any [offline client machines have the right certifica

When you install from a layout, the installer on the client always looks for the Visual Studio packages in the layout's location. However, if the installer tries to install components that are *not* included in the layout, then it will attempt to acquire the Visual Studio packages from the [update source](update-visual-studio.md#configure-source-location-of-updates-1), which administrators often configure to [point back to itself](automated-installation-with-response-file.md#configure-the-response-file-used-when-installing-from-a-layout).

> [!IMPORTANT]
> Remember that the layout location should remain the same for each Visual Studio instance.
> For more details, see [Install Visual Studio from the local layout](create-an-offline-installation-of-visual-studio.md#step-3---install-visual-studio-from-the-local-layout).

If you want to explicitly prevent the Visual Studio Installer from attempting to download any missing content from Microsoft hosted servers on the web, you can use the [`--noWeb` parameter](use-command-line-parameters-to-install-visual-studio.md#layout-command-and-command-line-parameters). If `--noWeb` is used and the layout is missing a component that is selected to be installed, then the setup will fail. Also, if `--noWeb` is used and the layout is hosted on your intranet web servers as opposed to a file network share, then the setup will fail.

Using the `--noweb` switch often fixes the error message "A product matching the following parameters can't be found".
Expand Down