CODEWITHSUNDEEP
c#nugettoolbardesigner
Soroush Falahati
Soroush Falahati

Reputation: 2337

Publishing Component with Dependency via NuGet and the Designer Toolbar

I have an open source Windows Form Control that is available for everyone to use via NuGet, however, this control depends on one of my other libraries for handling the animations.

Now the problem is that user won't see the control in the toolbox after adding the NuGet package and in fact, they can't even add the control manually because of its dependent to the other library and the fact that two libraries are in different folders.

So the question is, is there a better way to add a control to the Toolbar from a NuGet package? As for now, they need to compile their project once and then add the library from the /bin/Debug or /bin/Release folder to the toolbar.

The library in question is:

https://github.com/falahati/CircularProgressBar

Upvotes: 1

Views: 110

Answers (1)

Jeremy Thompson
Jeremy Thompson

Reputation: 65682

It seems NuGet is not built to handle these dependency scenarios and Designer Toolbox doesn't actually follow the added references to the project, as result it won't be able to add the control to the toolbox.

Given the situation that a dependency is causing the problem, it appears to be by-design (or unsupported).

I wanted to know if NuGet offers another way to put the dependent library next to the main library.

Have you tried to work around it by merging the 2 assemblies together. The tool ILMerge from Microsoft allows you to do just that. Here we merge Primary.dll Secondary.dll (and etc) into Merged.dll with a log.txt out of the merger.

ilmerge /log:log.txt /out:Merged.dll Primary.dll Secondary.dll

Upvotes: 2

Related Questions