This repository has been archived by the owner on Jul 12, 2022. It is now read-only.
Updater for packages.config files #31
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
||
| private async Task RunExternalCommand(string command) | ||
| { | ||
| var result = await _externalProcess.Run($"{command}"); |
There was a problem hiding this comment.
$"{command}" is exactly equivalent to command.
|
Very good, but we should also merge #28 first |
|
Needs re-doing following merge of #28 |
So that we can choose between 'dotnet add package' and 'nuget update' for updating the package
Even managed to sucessfully update some packages.
|
Re-done on current master |
This was referenced Aug 1, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This follows on #30 change
Uses NuGet.exe installed as a package, however, there's a problem: behaviour of this tool is not the same as updating through Visual Studio UI. Main difference seems to be that install/uninstall PowerShell scripts aren't run.
Examples:
https://www.nuget.org/packages/System.IO.Abstractions/ would add app.config assembly mappings, but command line doesn't do thisfor some reason this doesn't happen any more from UI eitherhttps://www.nuget.org/packages/StyleCop.Analyzers/ would update analyzers in .csproj, but command line doesn't do this