Last post Nov 15, 2007 01:37 PM by BGriffin_TPA
Jun 12, 2007 05:29 PM|dcapone|LINK
I have 2 web controls that I have developed seperately as seperate projects. One of the controls is a composite control that uses the other control.
What I am wondering is if there is a way to merge the 2 projects into a single assembly to make it less known that the composite control relies on another control.
The reason I ask is that the base control provides more functionality than the composite control and I'd like it hidden as much as possible. At the same time, I'd prefer to not just copy the source into the composite control project as then I knd of need
to maintain 2 seperate codebases. The ideal goal is to compile the composite control and have it output Composite.Control.dll ONLY, but whenever the base control is updated, the composite control just needs a new recompile.
Any way to accomplish this?
Jun 14, 2007 04:31 PM|jackyang|LINK
You can make your base control internal, and put 2 controls inside the same namespace under the same project.
|-- internal CompositeBase
|-- public Composite
Nov 15, 2007 01:37 PM|BGriffin_TPA|LINK
I hate coming into the discussion so late, but I have a closely related question.
I did my homework first:
I have a solution composed of 2 projects, my own and a web deployment project.
If I rebuild the web deployment with "Merge all outputs to a single assembly"
I get an XYZ.DLL as expected, but how does it work and what do I do with it?
It's in the \Release\Bin folder along with all the other parts that get created anyway.
I copy them to the \InetPub\wwwroot\ folder, and the site runs, but what did it actually
do? Do I have to include it in the web.config in the :
section? I see no performance difference with or without it. I'm missing something..[:S]
Thanks in advance..[cool]