Visual Studio 2013 / VB.NET / Cross solution web user controls
Posted on 2016-08-18
I have a web user control that I have developed for a particular solution in Visual Studio.
There is another solution that also needs the same web user control now.
How can I keep ONE code base for the web user control while still making it available to multiple solutions?
Can I put it into a DLL? Create a new solution dedicated to the web user control that has the needed dependencies?
What is the best practice?
Keep in mind that the web user control has dependencies. Up until now, this was not a problem because all of the needed dependencies resided in the same solution the web user control resides in. So those dependencies (i.e. bootstrap and moment.js) will also have to be made available (somehow) to other solutions who won't necessarily have the same structure or supporting files.