asked on

Visual Studio 2013 / VB.NET / Cross solution web user controls

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.

ASKER CERTIFIED SOLUTION

Éric Moreau

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Tom Knowlton

ASKER

So essentially -- a new solution that compiles as a DLL library?

Let me ask you, are there any gotchas / tips / tricks when attempting to write something that will be shared among solutions?

In other words, what are the top 5 common problems people run into when they try to do this sort of thing?

Tom Knowlton

ASKER

Thanks!

Éric Moreau

it is a project that will compile as a DLL. A solution is a set of various projects.

It is easier to debug your component if you create a solution with both your web application project and your component project. The debugger will be able to go from one to the other as if it was a single project.

Tom Knowlton

ASKER

Okay...thanks again!