First net 2.0 project, where is the DLL?

[Steve]

I can't find the DLL for my website? I found the aspx pages, but can't find
the dll. Please, someone clue me in please. Thank you.

 

[Rob R. Ainscough]

I had the exact same problem. To resolve the problem I ended up using
command line PreCompile approach along with XCOPY over to my web server.

aspnet_compiler.exe -v /<yourwebsite> -p <physical path to web app> <target
path for web app>

This is obviously a work around, but does take advantage of the new
PreCompile technology of ASP.NET 2.0 for "faster performance" -- it is a
little faster I must admit. But if you come across the real reason why the
DLL does not get created for your web app, please let me know.

Rob.

 

[Guest]

In Visual Studio 2005, click on Build -> Publish Web Site on the menu bar.
It will then ask you for a target location. Once you click OK, you will find
a bin directory within the target location that contains the DLL. You will
also find all the .aspx files and any dependencies (i.e. images) for your
application in the target location.

 

[Guest]

The main reason why the DLL is not created anymore by default has to do with
source control. Before ASP.NET 2.0, the DLL was checked into SourceSafe as
part of the application. This was a problem with team development because
everytime someone has to recompile the application, they have to check out
the DLL and lock out all others from compiling the application.

 

[Bruce Barker]

just like in 1.0, the page dll's are in a temp folder under the framework
ex:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET
Files\mysite

in 1.0 the codebehind dlls (actually all dll's in the bin folder) were
copied to these folders, and the pages (apsx) where compile into a dll. in
2.0, asp.net compiles the codebehind aslo, so no dll's are created in the
bin folder (this is for dll's included from other projects).

if you precompile the site for deployment, then VS makes a deploy folder
with all the dll's in the bin.

-- bruce (sqlwork.com)

 

[William LaMartin]

If you want to be able to deploy your web app as in VS 2003 where there is
just one DLL to be copied to the bin folder on the server and you then copy
all your aspx files and any other files you reference to the server also, I
suggest you go to
http://msdn.microsoft.com/asp.net/reference/infrastructure/wdp/default.aspx,
and download the Visual Studio 2005 Web Deployment projects along with the
instructions in the download further down the page: Using Web Deployment
Projects with Visual Studio 2005

It works real well for me.

 

[Scott Allen]

The main reason why the DLL is not created anymore by default has to do with
source control. Before ASP.NET 2.0, the DLL was checked into SourceSafe as
part of the application.

That's odd, I've never seen Visual Studio 2003 check a build output
into source control automatically.