Look into creating a Web Custom Control, then you can store the final
resulting control in a DLL; and re-use it across applications (either by
copying the DLL into the BIN directory of each application, or by installing
in the GAC).
This method also allows you to create/store client-side code (i.e.
javascript) within the control's DLL and render to the page when loading the
control.
I have set up several, and I have created designers for them as well, so
that they are now in my toolbox and I can just drag and drop them into a
form, change the properties that I need to, compile and run the application.
Works very nice.
Doing a search on MSDN.MICROSOFT.COM will bring up articles with
step-by-step guides. If you have trouble finding information, let me know.
Is this what you were looking for?
Thanks!
Jim
"Kelly Leahy" <> wrote in message
news:03dd01c3c5ac$ab016cf0$...
> >
> >"The virtual path '/Q/WebUserControl1.ascx' maps to
> >another application, which is not allowed."
>
> I just found a line in a book I have (Building ASP.NET
> Server Controls by Dale Milchalk and Rob Cameron (pretty
> good book IMHO) - APress publishers) that says "Resusing
> a user control [.ascx] requires copying its .ascx files
> along with code-behind assemblies, if necessary, in order
> to reuse it in different web applications." (page 75).
>
> Sounds to me that you can't share it without doing copy-
> paste sharing...
>
> Kelly
|