What I was referring to was to develop the "codebehind" classes in a class
library project and compile into a DLL. Then this DLL is referenced in the
web project, which has its own DLL. The web project would largely consists
of the aspx/ascx files. The web project compiles into a small DLL (pretty
much global.asax.cs). The classes in the first DLL are used in the aspx by
registering like this:
<%@ Register TagPrefix="AspNetForums" Namespace="AspNetForums.Controls"
Assembly="AspNetForums" %>
.........
<AspNetForums:LoginProcessor id="abc123" runat="server" />
.........
What I want to know is if I go with this kind of code separation, how do I
add an aspx or ascx without the VS.NET automatically sticks an
aspx.cs/ascx.cs file for me, as I don't need the cs files in the web project
itself, they are defined in the class library project.
"Kevin Spencer" <ke***@takempis.com> wrote in message
news:uW*************@tk2msftngp13.phx.gbl...
I don't understand the question. There are 2 components to an ASPX page:
The Page Template (.aspx) and the CodeBehind (.vb or .cs). The CodeBehind is
compiled into a DLL. The Page Template remains as text. You can't run the
app without both. There is a way to use CodeBehind without compiling to a
DLL. Is that what you're after?
--
HTH,
Kevin Spencer
Microsoft MVP
.Net Developer
http://www.takempis.com
Complex things are made up of
lots of simple things.
"BH" <bo*******@yahoo.com> wrote in message
news:On*************@TK2MSFTNGP09.phx.gbl... I'm looking at the source code of the ASP.NET forum sample application.
It has the "code-behind" classes compiled into a separate DLL, totally
separated from the aspx/ascx files. Adding the class files alone in
VS.NET is straightforward, but is there a way configure VS.NET to add aspx/ascx
files alone?
