Giter VIP home page Giter VIP logo

Comments (7)

aserie avatar aserie commented on June 2, 2024 1

I think the tool could have some better logging if it couldn't find MSBuild.exe. Looks like there is a check here if just one instance of MSBuild was found and shows the Multiple installs of MSBuild selector in all other cases (including the zero case).

try-convert uses MSBuildLocator to attempt to find MSBuild.exe on the machine to use. From my past experience, if you have ONLY a newer version of .NET SDK installed on your machine than what the tool is targeting, MSBuildLocator won't locate your newer SDK.

At the time of writing this, the released version of try-convert v0.9.232202 is targeting .NET5. Ensure you have the .NET5 x64 SDK installed on your machine and attempt to run try-convert again. You can check what installed versions you have by running dotnet --list-sdks.

Edit:
Looking a bit closer at MSBuildLocator, skipping SDKs that are newer than the apps targeted runtime is desired behavior.
microsoft/MSBuildLocator#92

from try-convert.

bwilliams1 avatar bwilliams1 commented on June 2, 2024

I ran into this issue as well. Running try-convert within a "Developer Command Prompt for VS 2019" seemed to work around it.

from try-convert.

twsouthwick avatar twsouthwick commented on June 2, 2024

Interesting. Can you run dotnet --list-sdks and paste the output?

from try-convert.

bwilliams1 avatar bwilliams1 commented on June 2, 2024

Interesting. Can you run dotnet --list-sdks and paste the output?

dotnet --list-sdks
5.0.403 [C:\Program Files\dotnet\sdk]
6.0.100 [C:\Program Files\dotnet\sdk]
6.0.101 [C:\Program Files\dotnet\sdk]

I did notice it works on a vanilla "cmd.exe" but reports the error on "Developer Command Prompt for VS 2022". all 3 command prompt versions report the same for "dotnet --list-sdks"

from try-convert.

twsouthwick avatar twsouthwick commented on June 2, 2024

Ah - in general, both try-convert and upgrade-assistant are expected to run in a terminal without the environment variables set by the developer command prompt. They set those variables internally and if they're already set it may conflict with resolution done by the tool.

from try-convert.

ATECoder avatar ATECoder commented on June 2, 2024

This is what I have (on the Visual Studio 2022 only VM):

6.0.200 [C:\Program Files\dotnet\sdk]

from try-convert.

modz2014 avatar modz2014 commented on June 2, 2024

i get the same issue as well

from try-convert.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.