vswhere | Locate Visual Studio 2017 and newer installations | Code Editor library
kandi X-RAY | vswhere Summary
kandi X-RAY | vswhere Summary
[chocolatey: all] over the years visual studio could be discovered using registry keys, but with recent changes to the deployment and extensibility models a new method is needed to discover possibly more than once installed instance. these changes facilitate a smaller, faster default install complimented by on-demand install of other workloads and components. vswhere is designed to be a redistributable, single-file executable that can be used in build or deployment scripts to find where visual studio - or other products in the visual studio family - is located. for example, if you know the relative path to msbuild,
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of vswhere
vswhere Key Features
vswhere Examples and Code Snippets
Community Discussions
Trending Discussions on vswhere
QUESTION
I have a build pipeline yaml file that looks like the following:
...ANSWER
Answered 2022-Mar-18 at 06:35Azure Devops build pipelines : build configuration in Yaml file not used
First, try to check if you missing build configuration in the Configuration Properties with Visual Studio or the checkbox of build is not checked.
Right clicking the solution, selecting "Properties" and then looking at the "Configuration Properties" property sheet:
Second, try to build and deploy it on your local to check if you have this issue, if not, please check the MSBuild version (Visual Studio Version) and the .net framework version with the version on the Azure devops.
QUESTION
I am getting the following error message, when i build the code using the Azure DevOps. The same code, when I build locally, I am able to build it successfully.
Warning MSB3245: Could not resolve this reference. Could not locate the assembly "Azure.Core, Version=1.20.0.0, Culture=neutral, PublicKeyToken=92742159e12e44c8, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
I am not able to figure out what am i missing here.
Following is the YAML FIle:
...ANSWER
Answered 2022-Jan-25 at 09:01You should not use paths that reference drives in azure pipelines tasks, as you don't have access to directories outside the scope of the pipeline agent, so in this case your nuget restore task does not work. Use predefined variables (https://docs.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml) when referencing, like:
QUESTION
ANSWER
Answered 2021-Dec-30 at 08:47Retrieving the MSBuild content into an artifact? Directory 'D:\a\1\a' is empty. Nothing will be added to build artifact 'drop'
That because the source of the task PublishBuildArtifacts
is $(Build.ArtifactStagingDirectory)
.
But the MSBuild task not generate the file in the $(Build.ArtifactStagingDirectory)
folder, so we need to copy the files from the output folder of the task MSBuild to the folder $(Build.ArtifactStagingDirectory)
by the copy task after MSBuild task:
QUESTION
I have Visual Studio 2019 and 2022 installed. I want to build boost libraries for 2019 vc142. How do I build vc142 libs instead of vc143?
My current method for building is as follows. I'm using Developer Command Prompt for 2019
, and running the following,
bootstrapper.bat
b2.exe install --prefix=MY_PATH
Unfortunately the output lib files are all vc143. I've also tried commenting out IF "%1"=="vc143" SET TOOLSET=msvc : 14.3
in bootstrap.bat with no success. One of the first outputs when running bootstrap.bat is Found with vswhere C:\Program Files\Microsoft Visual Studio\2022\Community
. I suspect this could be the problem
ANSWER
Answered 2021-Dec-20 at 15:36adding toolset=msvc-14.2
to the b2.exe builds the correct version.
b2.exe install --prefix=MY_PATH toolset=msvc-14.2
QUESTION
The package we used before (Microsoft.TeamFoundationServer.ExtendedClient), doesn't support netstandard2.0
and it seems that the new REST APIs doesn't support the tasks we want to accomplish either.
So what's the recommended way to add new files as pending changes or checkout existing files in tfvc when targeting netstandard2.0
?
TF.exe
should be capable of doing the aforementioned tasks, but to get the path to it we would somehow need vsWhere.exe
and so that whole approach seems a little bit cumbersome.
ANSWER
Answered 2021-Sep-29 at 12:49There is no, and won't be, a .NET Core compatible version of the TFVC client object model. The API used to interact with TFVC is a SOAP based API and it has never been ported to REST.
You can use vswhere to find tf.exe or build a custom .NET 4.x executable using the Client Object Model and call from your .NET Core app.
You're allowed to redistribute a copy of vswhere with your application. You can grab the latest version from here:
QUESTION
I am trying to create a Visual Studio Developer Powershell profile for Visual Studio Code. Here is what I tried:
...ANSWER
Answered 2021-Aug-04 at 16:10tl;dr
The following - which can be used as a property inside the "terminal.integrated.profiles.windows"
property of your settings.json
file in order to define a terminal profile named Developer PowerShell
- fixes the problems with your original attempt.
QUESTION
After installing Visual Studio 2019, I have problems with my anaconda. When I create a new environemnt in my anaconda, after hours I face the problem when I try to activate the environment and after that when I open any jupyter notebook, the kernel will not work. I copied the messages when I activate environment. How can I recover my anaconda environments? I have uninstalled the Visual Studio and deleted all its files but the problem is still here. I appreciate any help to solve this issue. I am using Windows 10 and Anaconda 3.
...ANSWER
Answered 2021-May-20 at 12:46It was solved by removeing the vs2017_compiler_vars
file that was in Anaconda3\envs\enviro\etc\conda\activate.d
.
QUESTION
Having trouble with CUDA + Pytorch this is the error. I reinstalled CUDA and cudnn multiple times.
Conda env is detecting GPU but its giving errors with pytorch and certain cuda libraries. I tried with Cuda 10.1 and 10.0, and cudnn version 8 and 7.6.5, Added cuda to path and everything.
However anaconda is showing cuda tool kit 9.0 is installed, whilst I clearly installed 10.0, so I am not entirely sure what's the deal with that.
...ANSWER
Answered 2021-Mar-20 at 10:44From the list of libraries, it looks like you've installed CPU only version of the Pytorch.
QUESTION
I'm attempting to capture the result from a vswhere command in JSON. When I run the command vswhere -legacy -format json
directly in the command line I get the following formatted JSON:
ANSWER
Answered 2020-Dec-19 at 03:37If you simply run the following program, without writing to standard input and using the Arguments, you can get the output you want.
QUESTION
Is there an MSTest.exe YAML equivalent in Github Actions Workflow?
If there is can a get sample yaml that includes how a /testcontainer
, /category
, and /resultsfile
would look like?
I was able to find MSBuild. Not sure if it's possible to use MsBuild to run MSTest's if it is then an example using the above would solve my question as well.
Current Workflow yaml
...ANSWER
Answered 2020-Nov-03 at 12:11Since you have msbuild at hand you should also be able to run mstest:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install vswhere
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page