The documentation lacks information about NuGet. #7282

Closed
opened 2026-01-31 00:59:56 +00:00 by claunia · 8 comments
Owner

Originally created by @jarkkojs on GitHub (Apr 5, 2020).

The documentation does not instruct to do nuget restore as part of the compilation steps.

Originally created by @jarkkojs on GitHub (Apr 5, 2020). The documentation does not instruct to do `nuget restore` as part of the compilation steps.
Author
Owner

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

This is because the default configuration of Visual Studio 2019 is to restore packages before building the solution, and some of the build scripts that are recommended in the readme do so as well.

@DHowett-MSFT commented on GitHub (Apr 5, 2020): This is because the default configuration of Visual Studio 2019 is to restore packages before building the solution, and some of the build scripts that _are_ recommended in the readme do so as well.
Author
Owner

@jarkkojs commented on GitHub (Apr 5, 2020):

I took the PS route:

Import-Module .\tools\OpenConsole.psm1
Set-MsBuildDevEnvironment
Invoke-OpenConsoleBuild

nuget restore fixed the issue.

What did I get wrong?

@jarkkojs commented on GitHub (Apr 5, 2020): I took the PS route: ``` Import-Module .\tools\OpenConsole.psm1 Set-MsBuildDevEnvironment Invoke-OpenConsoleBuild ``` `nuget restore` fixed the issue. What did I get wrong?
Author
Owner

@zadjii-msft commented on GitHub (Apr 6, 2020):

I'm not sure that you did anything wrong - Invoke-OpenConsoleBuild looks like it's supposed to call nuget restore

4f8acb4b9f/tools/OpenConsole.psm1 (L256-L260)

Did you happen to see any errors like "Error parsing solution file", or any errors related to nuget in the initial build that failed?

@zadjii-msft commented on GitHub (Apr 6, 2020): I'm not sure that you did anything wrong - `Invoke-OpenConsoleBuild` looks like it's supposed to call `nuget restore` https://github.com/microsoft/terminal/blob/4f8acb4b9fbd61196d0a5287749a58abe0fbaa28/tools/OpenConsole.psm1#L256-L260 Did you happen to see any errors like "Error parsing solution file", or any errors related to `nuget` in the initial build that failed?
Author
Owner

@ghost commented on GitHub (Apr 10, 2020):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Apr 10, 2020): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Author
Owner

@WSLUser commented on GitHub (Apr 10, 2020):

We also need to document how we're even using Nuget in this project.

@WSLUser commented on GitHub (Apr 10, 2020): We also need to document how we're even using Nuget in this project.
Author
Owner

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

And why is that? We're using it for packages.

@DHowett-MSFT commented on GitHub (Apr 10, 2020): And why is that? We're using it for packages.
Author
Owner

@WSLUser commented on GitHub (Apr 10, 2020):

Indeed but what Nuget packages are in use? I can't even find most of the deps available through the public Nuget feed. We also aren't creating a .net app either. It seems like our deps are supposed to update through this method but they weren't created with .net in mind and we utilize them in C++. It's just a bit confusing on how all the pieces fit together. Maybe if we had a more detailed design flow schematic in the docs, this would be a bit more clear for contributors.

@WSLUser commented on GitHub (Apr 10, 2020): Indeed but what Nuget packages are in use? I can't even find most of the deps available through the public Nuget feed. We also aren't creating a .net app either. It seems like our deps are supposed to update through this method but they weren't created with .net in mind and we utilize them in C++. It's just a bit confusing on how all the pieces fit together. Maybe if we had a more detailed design flow schematic in the docs, this would be a bit more clear for contributors.
Author
Owner

@ghost commented on GitHub (Apr 14, 2020):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Apr 14, 2020): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7282