Skip to content

BuildGVFSForWindows.bat: use nuget on PATH when possible#1679

Merged
derrickstolee merged 1 commit intomicrosoft:masterfrom
derrickstolee:nuget-problem
Jun 23, 2020
Merged

BuildGVFSForWindows.bat: use nuget on PATH when possible#1679
derrickstolee merged 1 commit intomicrosoft:masterfrom
derrickstolee:nuget-problem

Conversation

@derrickstolee
Copy link
Contributor

Our release build is failing because we cannot download nuget due to TLS
1.2 changes. But we already require nuget.exe in an earlier step of the
build.

Require nuget.exe to be on the PATH, and update Readme.me accordingly.

Our release build is failing because we cannot download nuget due to TLS
1.2 changes. But we already require nuget.exe in an earlier step of the
build.

Require nuget.exe to be on the PATH, and update Readme.me accordingly.

Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
@derrickstolee derrickstolee merged commit dcde05c into microsoft:master Jun 23, 2020
derrickstolee added a commit that referenced this pull request Jul 28, 2020
Major Updates
-----------------

* Comes with Git for Windows 2.28.0
* Previous builds were not including fully-signed DLLs. This is now fixed.

Pull Requests
---------------

* #1672: ProductUpgrader: be extra careful about a copy loop
* #1674: Config: disable status.submoduleSummary
* #1675: PreCommandHook: don't lock pack-objects 
* #1676: Update Git to v2.27.0.vfs.1.0 
*  #1679: BuildGVFSForWindows.bat: use nuget on PATH
* #1683: GVFS.SignFiles.csproj: include more DLLs for signing
* #1685: minor path comparison fixup in ProductUpgrader
*  #1682: Update Git to v2.28.0
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

Successfully merging this pull request may close these issues.

2 participants