Thanks for Tim's input!
Hi Max,
Yes, as Tim suggested, for web application, you can easily reuse the codes
via define common classes or base classes and separate them into a class
library.
However, for aspx page or other page stuffs, it is not quite convenient and
practical to separate them into separate projects because diffrent project
may result to different Application context(such as appdomain, cache,
sessionstate boundary...) and it will be much difficult for you develop the
pages' code and coordinate them.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>From: "Tim Mackey" <ti********@community.nospam>
References: <Ol**************@TK2MSFTNGP05.phx.gbl>
In-Reply-To: <Ol**************@TK2MSFTNGP05.phx.gbl>
Subject: Re: A solution with multiple web projects and ASPX page
reusability
>Date: Mon, 1 Oct 2007 16:06:26 +0100
>
hi max
the easiest step is to place the code behind files in a class library
project and compile them. then you can refer to the full namespace of the
code behind class in the Inherits attribute in your ASPX page declaration.
this way you at least get to re-use the codebehind, although you would
still
>have to deploy the ASPX file itself. there is also a way of compiling
ascx
>pages into a binary, http://msdn2.microsoft.com/en-us/library/aa479318.aspx
hope this helps
tim
"Max2006" <al*******@newsgroup.nospamwrote in message
news:Ol**************@TK2MSFTNGP05.phx.gbl...
>Hi,
Is there any way to break a web application into separated web projects,
so we can re-use pages\?
I am trying to put aspx pages and/or ascx pages in separated web
projects,
>but when we run the solution, the start-up web project contain all
necessary aspx/ascx pages + dlls to run.
Any help would be appreciated,
Max