Nuget Dependency Problem (NServiceBus)
-
I have an internal nuget. It pulls in the nuget for NSB 7.5. The dependency info clearly shows it is pulling in 7.5. However, when I then pull my internal nuget into a project, it attempts to put NSB 8.0 as the transient NSB dependency for the internal nuget. I do not at all understand why this is happening or how to fix it. Has NSB messed up their nugets? What am I missing? Help. Please.
-
I have an internal nuget. It pulls in the nuget for NSB 7.5. The dependency info clearly shows it is pulling in 7.5. However, when I then pull my internal nuget into a project, it attempts to put NSB 8.0 as the transient NSB dependency for the internal nuget. I do not at all understand why this is happening or how to fix it. Has NSB messed up their nugets? What am I missing? Help. Please.
-
Why have you posted this in the C# forum? It clearly has nothing to do with writing C# code.
-
Well that does not explain anything. If you want people to help you then you need to give proper details of your problem. And I still cannot see anything relevant to C# in your question.
Nevermind, I'll ask stack overflow. They're nicer about these things. ;P Seriously, this is the first thing I think I've ever asked here. Maybe .NET would be better, but I think if there are people who would have this answer they more likely to poke here.
-
Nevermind, I'll ask stack overflow. They're nicer about these things. ;P Seriously, this is the first thing I think I've ever asked here. Maybe .NET would be better, but I think if there are people who would have this answer they more likely to poke here.
-
Why have you posted this in the C# forum? It clearly has nothing to do with writing C# code.
-
jochance wrote:
Seriously, this is the first thing I think I've ever asked here.
Well after the other 300 odd messages you should know what the process is.
-
Is there a better forum to ask questions about VS projects? I can seem some overlap with others (like Managed C++) but nothing that seems to be specific about VS Projects.
It could go in .NET Core but... It's just the case here is going to more likely get the right eyes. It doesn't really matter now. Fixed. (another nsb nuget was the cause, it required higher, so it was forcing it to pull a higher version - that nsb nuget was only in the top-level, so wasn't seeing that happen pulling this same thing into others). My biggest beef is just the absolute ham-fisted pedantry. But it isn't like I ask or answer questions much here nor is it exactly inspiring to do so in the future. Maybe that's the point? Imaginary internet point hoarding? Maybe it's just been a long day. Will never much care for that kind of stuff though.
-
Is there a better forum to ask questions about VS projects? I can seem some overlap with others (like Managed C++) but nothing that seems to be specific about VS Projects.
I suspect the more appropriate forum would have been .NET (Core and Framework)[^] or, better still, QA.
-
Is there a better forum to ask questions about VS projects? I can seem some overlap with others (like Managed C++) but nothing that seems to be specific about VS Projects.
-
I don't see anything in the question relevant to VS either. And I did ask OP to clarify his problem, but seems he wasn't interested.
Richard MacCutchan wrote:
relevant to VS either
From the post "when I then pull my internal nuget into a project," I figured that mean using a project via VS. One can manage them outside of VS but I doubt many people do. Certainly I would presume that most do it in VS so that is how I read it.