One thing you can do is build a dll and then install this dll into the GAC.
Note, however, that your declarative code won't be included in the compiled
dll (these are compiled on the fly - only the code behind is pre-compiled)
so you'll have to do your dirty work in code instead of using the nice
designer, but it is an effective alternative. Another option is to actually
just call the pages you want from an internal object that can post to the
page, and then just render the HTML that is returned.
--
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)
--
"Jon Paugh" <an*******@discussions.microsoft.com> wrote in message
news:0c****************************@phx.gbl...
Hi,
If I have several aspx pages that I want to share across
multiple web applications, how would I organize them?
Basically, a subset of the pages on a given site will be
on several sites. These pages will interact with a
database, check security, etc.
I have seen this KB article:
http://support.microsoft.com/default.aspx?kbid=324785
but my concern is how to handle authentication +
authorization on the shared virtual directory? Putting a
virutal directory under the current web app and have this
virtual directory point to another asp.net web app seems
like a cute way to do share some user controls but not a
way to handle pages that do anything meaningful...
Any ideas?
Jon Paugh