find arg Returns matching file paths under the installation path. Use delimiters ".", "/", or "_" to separate object and property names.Įxample: "properties.nickname" will return the "nickname" property under "properties". property arg The name of a property to return. format arg Return information about instances found in a format described below. This option cannot be used with either -products or -requires. legacy Also searches Visual Studio 2015 and older products. When used with "find", first instances are sorted then files are sorted lexigraphically. sort Sorts the instances from newest version and last installed to oldest. latest Return only the newest version and last installed. version arg A version range for instances to find. requiresAny Find instances with any one or more workload or components IDs passed to -requires. See for a list of workload and component IDs. requires arg One or more workload or component IDs required when finding instances.Īll specified IDs must be installed unless -requiresAny is specified. Specify "*" by itself to search all product instances installed. Defaults to Community, Professional, and Enterprise. products arg One or more product IDs to find. all Finds all instances even if they are incomplete and may not launch. Visual Studio Locator version 2.6.13+a6d40ba5f4 Ĭopyright (C) Microsoft Corporation. PS D:\builds\dev-agent-1\externals\vswhere>. Let’s see what options are available by calling vswhere.exe –help :.Go to the externals\vswhere subfolder.Login on your build server and open the installation folder of one of your build agents.Vswhere is installed as one of the tools of the build agent, but in case of trouble you can run it yourself to see what is going wrong. This is all done through vswhere.exe, a tool I blogged about before. If everything is OK, you should see something like this in your Build Agent capabilities:īut how does the build agent detects that Visual Studio is there? As Visual Studio is not added to the capabilities of the build agent, the specific agent is never used to conduct a build. I’ve seen a few times where the build agent didn’t pick up the Visual Studio installation, making the build server useless. Detecting if Visual Studio is installed on the build server can be quite painful.