Re: what's different between asp application and web site

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

a web application has a project file, and visual studio compiles the codebehinds into a dll, and the asp.net (or the aspnet_compiler in precompiled sites) compiles the aspx pages into dll's. this is more compatible with vs2003 projects as codebehind files can refer to publics in each other.

a web site has no project file, and asp.net (or the aspnet_compiler if precomplied) includes the codebehind with the page dlls. this means pages can not refer to each other, interfaces should be used (the 2003 conversion wizard would do this).

in either case you should should use a deployment project which will maintain the the pages and binaries needed to deploy in a separate folder system (say your application server). deployment projects can also edit the web.config settings.

-- bruce (sqlwork.com)

william wrote:
Hi,

I posted this in wrong group, so just re-post here.
There are two ways to create web-based application or web service, from VS start page, click on File and New, two options you can choose, one is Projects which leads you to create ASP.NET Web Application or ASP.NET Web Service Application. Another one is Web Site which leads you to create ASP.NET Web Site or ASP.NET Web Service. My question is what is the difference between these two ways. Especially in terms of production performance, maintainance, resource consuming. I got an answer saying compatibility is slightly different from VS2003.
Anyway what's the real difference except compatibility?
The reason I'm asking this question is that I am designing an upgrading system from VB6 to .NET, it will be web-based SOA system. I used VS2003 for developing web application and web service, when I deploy them, I deploy all BLL assemblies at centrolized location on application server instead of having a copy of them under web bin folder. But in VS2005, if I use creating web site approach, all referenced dlls will be included under bin folder, and any time if any dll has been changed, I need to deploy it both places.


Thanks.

William

.

Relevant Pages

  • Re: Namespaces - broad question
    ... aspx pages that I know I want utilize a specific function within, ... have the same codebehind page), how can I reference this function. ... >> compiling if the same class was written in different places. ... > A .Net assembly is a compiled DLL. ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: lack of .NET project file on web server
    ... I think you need a good dose of "big picture" with .NET web development. ... The project file did not have to be deployed to the live web ... server since it was only used by the deveopment environment. ... files are compiled into a DLL. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Newbie Question: Moving code to external file
    ... Codebehind classes ... the codebehind assembly (roughly equivalent to a .dll) for the webproject. ... toolbar control could be written as custom web controls. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Maintaining ASP.NET application
    ... Codebehind is stored in your application dll. ... There are standard methodologies for this ... > I am on the brink of deciding which language to use for a $200,000 ...
    (microsoft.public.dotnet.faqs)
  • Re: New to ASP
    ... imagine that the dll would be included. ... laptop, but thinking about it, it is the older version and not 1.1. ... The exact error message that I am getting is "Unable to get the project file ... > You did install the .net framework on your laptop? ...
    (microsoft.public.dotnet.framework.aspnet)