I'm having a few problems with the fact that the nuget package for Resharper's SDK is a huge mess of dlls (140mb).
I posted this recently on stackoverflow:
I had to checkin the whole sdk, which amounts to 80mb of dlls, to the TFS source control custom assemblies path so that I could finally use my modified workflow.
Have you guys thought about splitting this huge nuget package in manageable parts? How can someone reference it and carry such an enourmous amount of useless unrelated dlls? I mean, in my case, I only needed a very small subset of them to achieve what I wanted.
Also, have you thought about creating a .Net4.5 version of that package? I see it uses things like AsyncBridge for compatibility with .Net4 for instance, but I would like to avoid that since my project is 4.5.
And lastly, why are some external dependencies of your SDK not dependencies on the package? AsyncBridge for instance is available as a separate package. Why did you include it in your own package instead of saying your package depends on it? The same can be said for other dlls in there, like DevExpress, WpfContrib. Also, what is nunit doing here? I see you are shipping some UnitTests dlls in there too....
I'm sorry, but there are so many bad practices here that it is hard to believe the package came from you guys. Was this all really intentional?