-
Notifications
You must be signed in to change notification settings - Fork 520
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Group Main was not found when calling Dependencies.Remove for last dependency #1950
Comments
I get the same behaviour if I try to remove the last NuGet dependency using
|
Paket currently throws an error when removing the last NuGet package: Group Main was not found in paket.dependencies. fsprojects/Paket#1950 This left the UI and files still showing the original information even though Paket does remove the NuGet package from the dependencies and references files. So now the addin still notifies that these files have changed when there was an error removing a NuGet package. This ensures the Solution window is updated with the correct information and the files are reloaded if they are open in the text editor.
Should be fixed in latest version. Can you please retry? |
I am still seeing the same error with Paket 3.25.2.0
|
Shit thought another thing fixed it as well. Will take another look next Am 29.10.2016 14:46 schrieb "Matt Ward" [email protected]:
|
Description
Programmatically removing the last NuGet package from a paket.dependencies file, using Dependencies.Remove, throws an 'Group Main was not found' exception.
Paket version: 3.21.4
Repro steps
Create a paket.dependencies file containing a single NuGet package:
source https://www.nuget.org/api/v2
nuget NUnit
Install the NUnit NuGet package using paket install
3, Then programatically remove the NUnit NuGet package using code similar to the following C# code:
Expected behavior
The NuGet package is removed from the paket.dependencies file without any exception.
Actual behavior
The NuGet package is removed from the paket.dependencies file but an exception is thrown.
Known workarounds
If the paket.dependencies file has two NuGet packages (e.g. NUnit and jQuery) then removing the NUnit package works without any exception being thrown.
The text was updated successfully, but these errors were encountered: