build: either update nuget.exe in the repo or delete it and figure out a replacement for commandline build #7654

Open
opened 2026-01-31 01:09:39 +00:00 by claunia · 2 comments
Owner

Originally created by @dynahcatq on GitHub (Apr 24, 2020).

Environment

Windows build number: [Version 10.0.19041.208]
Windows Terminal version (if applicable): master branch commit ID: a76cee1d98c4368815013eaccc09c6f0d3fe62e9

Steps to reproduce

I was following this build doc for building in cmd.

1. clone this repo
2. cd into terminal folder
3. run git submodule update --init --recursive
4. run .\tools\razzle.cmd
5. The previous command will success but show:
        Setting up dev environment...
        Error parsing solution file at C:\Users\dynahcatq\OpenSource\terminal\OpenConsole.sln: Exception 
        has been thrown by the target of an invocation.
        The dev environment is ready to go!
6. run bcz
7. Then observe error:
        error : This project references NuGet
        package(s) that are missing on this computer. Use NuGet Package Restore to download them.
8. run nuget restore will also gives this error:
        Error parsing solution file at C:\Users\dynahcatq\OpenSource\terminal\OpenConsole.sln: Exception has been thrown by the target of an invocation.
9. run nuget update -self (This workaround will solve the problem)

It seems like the dep/nuget/nuget.exe is outdated (NuGet Version: 4.1.0.2450) and the .\tools\razzle.cmd will set PATH to use this outdated nuget. The nuget update -self will update it to latest version 5.5.1. Should we update nuget.exe in this repository?

Expected behavior

The dep\nuget should provide correct version to build, or the doc should be updated.

Actual behavior

The provided dep\nuget gives error when try to do nuget restore, the build with cmd process failed.

Originally created by @dynahcatq on GitHub (Apr 24, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [Version 10.0.19041.208] Windows Terminal version (if applicable): master branch commit ID: a76cee1d98c4368815013eaccc09c6f0d3fe62e9 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> I was following this [build](https://github.com/microsoft/terminal/blob/master/doc/building.md) doc for building in cmd. ```none 1. clone this repo 2. cd into terminal folder 3. run git submodule update --init --recursive 4. run .\tools\razzle.cmd 5. The previous command will success but show: Setting up dev environment... Error parsing solution file at C:\Users\dynahcatq\OpenSource\terminal\OpenConsole.sln: Exception has been thrown by the target of an invocation. The dev environment is ready to go! 6. run bcz 7. Then observe error: error : This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. 8. run nuget restore will also gives this error: Error parsing solution file at C:\Users\dynahcatq\OpenSource\terminal\OpenConsole.sln: Exception has been thrown by the target of an invocation. 9. run nuget update -self (This workaround will solve the problem) ``` It seems like the dep/nuget/nuget.exe is outdated (NuGet Version: 4.1.0.2450) and the .\tools\razzle.cmd will set PATH to use this outdated nuget. The `nuget update -self` will update it to latest version 5.5.1. Should we update nuget.exe in this repository? # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> The dep\nuget should provide correct version to build, or the doc should be updated. # Actual behavior <!-- What's actually happening? --> The provided dep\nuget gives error when try to do nuget restore, the build with cmd process failed.
claunia added the Issue-TaskProduct-MetaArea-BuildArea-CodeHealth labels 2026-01-31 01:09:39 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 25, 2020):

Thanks for the report! I'm going to look at properly deprecating NuGet.exe here -- it's actually impossible (various reasons) for you to build Windows Terminal for development scenarios and get it working strictly using the commandline. You'll have much better luck using VS than trying to follow our commandline build instructions.

@DHowett-MSFT commented on GitHub (Apr 25, 2020): Thanks for the report! I'm going to look at properly deprecating NuGet.exe here -- it's actually impossible (various reasons) for you to build Windows Terminal for development scenarios and get it working strictly using the commandline. You'll have much better luck using VS than trying to follow our commandline build instructions.
Author
Owner

@dynahcatq commented on GitHub (Apr 26, 2020):

Yea, I later encountered a circular dependency error while building. Then I tried to build with VS and it works like charm.

@dynahcatq commented on GitHub (Apr 26, 2020): Yea, I later encountered a circular dependency error while building. Then I tried to build with VS and it works like charm.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7654