Skip to content
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

support multiple item groups #44

Open
aliasadidev opened this issue Aug 4, 2022 · 7 comments
Open

support multiple item groups #44

aliasadidev opened this issue Aug 4, 2022 · 7 comments
Assignees

Comments

@aliasadidev
Copy link
Owner

No description provided.

@aliasadidev aliasadidev self-assigned this Aug 4, 2022
@eburnette
Copy link

I ran into this one. I can't open my project because it has multiple item groups, some of which are conditional. The NuGet Package Manager GUI just spins and never finishes loading. I get an error about "More than one find."

@jobou363
Copy link

jobou363 commented Nov 4, 2022

I have also the same problem because in have 3 items groups. It seems I can't regroup and use one.

@mikes-gh
Copy link

mikes-gh commented Dec 5, 2022

This is unfortunate because this is the best tool out there. But I am multi targeting net6 net7 as I suspect a few others are making this extension non-functional. Mind you dependabot cant cope with this either (although it doesnt crash)

@aliasadidev aliasadidev added the enhancement New feature or request label Feb 24, 2024
@davidsr2r
Copy link

Facing the same issue here, quite annoying!

@enny1170
Copy link

enny1170 commented Jun 4, 2024

Same problem here in a MAUI Project. I can't change to singe ItemGroup because the others has conditions needed. Pls find a way to support multiple item groups

@Ghostbird
Copy link

Ghostbird commented Sep 3, 2024

Yeah, I tried this extension, but it's completely useless because of this odd restriction. I did a brief scan of the code, and I think it's because the package reference elements are identified by index. That's a strange design choice that introduces all kinds of seemingly arbitrary restrictions. My first take on writing something like this, is that the package reference elements should be identified by their Include value.

For a quick estimate, I checked the repositories I currently have cloned on my machine, and out of 20 projects, only 2 had less than 2 ItemGroups. But those two were projects that only defined a few models and were referenced by other projects in the same solution. So for those repositories the extension still didn't work, as the referencing project file did have multiple ItemGroups.

Conclusion: Because of this arbitrary restriction, this extension cannot work in any of my normal use cases.

@aliasadidev
Copy link
Owner Author

I started it

@aliasadidev aliasadidev removed the enhancement New feature or request label Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants