Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error after installing VS 2022 and updating OS to Win 10 20H2 #22

Closed
br549times3 opened this issue Jan 14, 2022 · 6 comments
Closed

Error after installing VS 2022 and updating OS to Win 10 20H2 #22

br549times3 opened this issue Jan 14, 2022 · 6 comments

Comments

@br549times3
Copy link

br549times3 commented Jan 14, 2022

I have build tasks that use devenv and they were working, but after installing VS 2022 and also updating Windows 10 from 1803 to 20H2 version and also WSL 2.0 if it has any impact.

I am getting error:

Description : Build a project via the visual studio command-line invocation, devenv.cmd. Used for building eg. SSIS projects.
Version : 2.0.5
Author : Mario Majcica
Help : Build your project via the visual studio command-line invocation, devenv.cmd

##[error]Cannot process argument transformation on parameter 'FileName'. Cannot convert value to type System.String.

image

@br549times3
Copy link
Author

My task setting is set to VS 2019 and using a path: Common/File.sln

@henrypedersen77
Copy link

We have the same issue, after installing VS 2022 on the build server, then all our piplines that uses this component is failing, withe the same error message. Are you looking into fixing this issue? Please :-)

@chm2305
Copy link

chm2305 commented Feb 9, 2022

Same issue her :-(

@Gitprojekter
Copy link

All our devops pipelines that uses this component is failing and we have around 80 pipelines which build using VS2019 and not VS2022.
Why VS2022 impact this component I don't have any idea.

We have a release in 2 weeks where we should be able to build from the build server. It will be a big job to replace all our builds with something else, because we are otherwise happy with this component.

Do you have any idea when you can have a fix that solve issue.

@cbolsen
Copy link

cbolsen commented Mar 22, 2022

I'm seeing the same issue after installing VS2022 on the build server, even if I set the version option to "Visual Studio 2019".

@cbolsen
Copy link

cbolsen commented Mar 22, 2022

The problem was resolved by removing VS2019. It seems the task has trouble resolving the path when more than one version is installed, similar to #11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants