You could always develop a class library. Expose a class called
MyCompany.MyApplication.PageWithControls, which derives from
System.Web.UI.Page. Then, implement the controls on this page. Compile and
strong name this class, then install it in the GAC. Both applications can
now find this assembly and bind to it. Then, in both of your applications,
have your new pages derive from MyCompany.MyApplication.PageWithControls.
When you need to update the base class, you need only update the assembly
that implements PageWithControls, and the changes will cascade to all other
applications which derive from this class.
--
Chris Jackson
Software Engineer
Microsoft MVP - Windows Client
Windows XP Associate Expert
--
More people read the newsgroups than read my email.
Reply to the newsgroup for a faster response.
(Control-G using Outlook Express)
--
"Joel Barsotti" <jo**********@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
I'm building two applications for one website, one is the public website
and
the other is our private admin site.
Fors some of the sales processing utilities I'm using user controls to
contain some logic of thing like credit card input, user registration.
Is there a way to get around this?
What I was thinking was doing an include to contain the body of the ASCX
page and having the codebehind page directly inherit the the class for the
original control.
Is there another way to do this?
My goal here is to be able to make updates in one place and have them
cascaade through both applications.
Could I set it up as a vitural directory?