razzle.cmd should prepend the path to the nuget.exe from our repo #1480

Closed
opened 2026-01-30 22:28:24 +00:00 by claunia · 3 comments
Owner

Originally created by @ThadHouse on GitHub (Jun 2, 2019).

Attempting to build from cmd is giving the following output. Made sure the repo was in root so there was no too long of path issues.

C:\terminal>.\tools\razzle.cmd
Setting up dev environment...
WARNING: Error reading msbuild project information, ensure that your input solution or project file is valid. NETCore and UAP projects will be skipped, only packages.config files will be restored.
WARNING: NU3028: The author primary signature's timestamp found a chain building issue: InvalidExtension
WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension
WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension
WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension
WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension
WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension
WARNING: NU3028: The author primary signature's timestamp found a chain building issue: InvalidExtension
WARNING: NU3018: The author primary signature found a chain building issue: UntrustedRoot
WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot
WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot
WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot
WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot
WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot
WARNING: NU3018: The author primary signature found a chain building issue: UntrustedRoot
WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension
WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension
WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension
WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension
WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension
WARNING: NU3028: The author primary signature's timestamp found a chain building issue: InvalidExtension
WARNING: NU3028: The author primary signature's timestamp found a chain building issue: InvalidExtension
WARNING: NU3018: The author primary signature found a chain building issue: UntrustedRoot
WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot
WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot
WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot
WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot
WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot
WARNING: NU3018: The author primary signature found a chain building issue: UntrustedRoot

C:\terminal>bcz
Starting build...
MSBuild auto-detection: using msbuild version '16.1.76.45076' from 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\bin'.
All packages listed in packages.config are already installed.
Building Appx...
"" C:\terminal\OpenConsole.sln /t:Clean,Build /m /p:Configuration= /p:Platform=
'""' is not recognized as an internal or external command,
operable program or batch file.

It seems weird that Platform is empty and forcing a new line in the Platform parameter.

Is there any way I can turn on more logging for these commands?

Originally created by @ThadHouse on GitHub (Jun 2, 2019). Attempting to build from cmd is giving the following output. Made sure the repo was in root so there was no too long of path issues. ``` C:\terminal>.\tools\razzle.cmd Setting up dev environment... WARNING: Error reading msbuild project information, ensure that your input solution or project file is valid. NETCore and UAP projects will be skipped, only packages.config files will be restored. WARNING: NU3028: The author primary signature's timestamp found a chain building issue: InvalidExtension WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension WARNING: NU3028: The author primary signature's timestamp found a chain building issue: InvalidExtension WARNING: NU3018: The author primary signature found a chain building issue: UntrustedRoot WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot WARNING: NU3018: The author primary signature found a chain building issue: UntrustedRoot WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension WARNING: NU3028: The repository primary signature's timestamp found a chain building issue: InvalidExtension WARNING: NU3028: The author primary signature's timestamp found a chain building issue: InvalidExtension WARNING: NU3028: The author primary signature's timestamp found a chain building issue: InvalidExtension WARNING: NU3018: The author primary signature found a chain building issue: UntrustedRoot WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot WARNING: NU3018: The repository primary signature found a chain building issue: UntrustedRoot WARNING: NU3018: The author primary signature found a chain building issue: UntrustedRoot C:\terminal>bcz Starting build... MSBuild auto-detection: using msbuild version '16.1.76.45076' from 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\bin'. All packages listed in packages.config are already installed. Building Appx... "" C:\terminal\OpenConsole.sln /t:Clean,Build /m /p:Configuration= /p:Platform= '""' is not recognized as an internal or external command, operable program or batch file. ``` It seems weird that Platform is empty and forcing a new line in the Platform parameter. Is there any way I can turn on more logging for these commands?
Author
Owner

@zadjii-msft commented on GitHub (Jun 3, 2019):

Well something went crazy wrong before you executed bcz. Looks like nuget totally exploded trying to restore packages. Unfortunately, I'm not much of an expert in nuget, so I don't really know how to debug nuget errors....

I'd maybe try manually installing a fresh nuget, and using that to restore the packages for our repo, instead of relying on the version we ship with the repo. Looks like there are some missing certs, but I can't really tell from that message if it's a cert that's missing on your PC, or something wrong with the packages online :/

@zadjii-msft commented on GitHub (Jun 3, 2019): Well something went crazy wrong before you executed `bcz`. Looks like nuget totally exploded trying to restore packages. Unfortunately, I'm not much of an expert in nuget, so I don't really know how to debug nuget errors.... I'd maybe try manually installing a fresh nuget, and using that to restore the packages for our repo, instead of relying on the version we ship with the repo. Looks like there are some missing certs, but I can't really tell from that message if it's a cert that's missing on your PC, or something wrong with the packages online :/
Author
Owner

@ThadHouse commented on GitHub (Jun 4, 2019):

Turns out this was caused by having my Mono install in my Path, and the NuGet from that install was getting picked up, and causing the breakage.

Maybe https://github.com/microsoft/terminal/blob/master/tools/razzle.cmd#L24 should point directly to the NuGet exe rather then going through path, or put the deps path before the existing path in the line above. Don't know if either of those will break anything though.

@ThadHouse commented on GitHub (Jun 4, 2019): Turns out this was caused by having my Mono install in my Path, and the NuGet from that install was getting picked up, and causing the breakage. Maybe https://github.com/microsoft/terminal/blob/master/tools/razzle.cmd#L24 should point directly to the NuGet exe rather then going through path, or put the deps path before the existing path in the line above. Don't know if either of those will break anything though.
Author
Owner

@zadjii-msft commented on GitHub (Jun 4, 2019):

Yea we could probably make razzle (and bcz) manually use that path. I'm not sure what kind of side-effects prepending our nuget might have, but I'd think they'd be minimal. Presumably, if you run razzle, you want to be in our dev space, not something else, so I think it'd be fine.

This wouldn't be a terribly challenging code change if someone wanted to pick it up :)

@zadjii-msft commented on GitHub (Jun 4, 2019): Yea we could probably make razzle (and bcz) manually use that path. I'm not sure what kind of side-effects prepending our nuget might have, but I'd think they'd be minimal. Presumably, if you run `razzle`, you want to be in our dev space, not something else, so I think it'd be fine. This wouldn't be a terribly challenging code change if someone wanted to pick it up :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#1480