This wouldn't be necessary if folks would name nugets uniquely, but it's an imperfect world.
Let's say that you have a nuget dependency on something called "log4net", and there are two similarly named, yet different nugets available on 2 different feeds:
1.) log4net.2.0.0 is available on Feed #1 one signature
2.) log4net.2.0.0.0 is available on Feed #2, but it has a completely different strong name
In this case it might be important to say that we absolutely have to get log4net.2.0.0 from one feed or another because they aren't really compatible.
In other news, we really need the solution where we just rip the strong naming out as we download assemblies
This wouldn't be necessary if folks would name nugets uniquely, but it's an imperfect world.
Let's say that you have a nuget dependency on something called "log4net", and there are two similarly named, yet different nugets available on 2 different feeds:
1.) log4net.2.0.0 is available on Feed #1 one signature 2.) log4net.2.0.0.0 is available on Feed #2, but it has a completely different strong name
In this case it might be important to say that we absolutely have to get log4net.2.0.0 from one feed or another because they aren't really compatible.
In other news, we really need the solution where we just rip the strong naming out as we download assemblies