473,320 Members | 2,094 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,320 software developers and data experts.

Difference between ASP.NET Website and ASP.NET Application Project

What, from a high level point of view, is the difference (in Visual
Studio 2005) between Website (accessed with Open Website or Create
Website from the StartPage) that is an ASP.NET Website, and a Project
that is created with the "ASP.NET Application" template?

I see some obvious differences: the Project creates the working folder
under the Visual Studio 2005\Projects directory, while the Website
creates it in the Inetpub\wwwroot directory. And there are some more
subtle differences that I don't understand as well. The project
creates some .cs (in C#) files for a lot of the things that the
website does not (e.g., in the Website, there is no .cs file generated
for DataSets (.xsd files), and theres no <page>.designer.cs file
generated for pages). The project uses different namespace
definitions for the same files in the same relative directory
positions. And it seems that some of the web administration tools (the
whole Website menu, including "Copy Web") is missing when you're
working with a project. Also, it appears (I'm not sure) that the
compiled code for the website is never stored (it seems to be being
regenerated on the fly when I access the website.)

I see these differences, but I don't understand why they're there or
to what purpose they are there. Can someone explain it to me?

Thanks.
Jun 27 '08 #1
5 2981
On 17 Apr, 18:41, daveh551 <gee...@gmail.comwrote:
What, from a high level point of view, is the difference (in Visual
Studio 2005) between Website (accessed with Open Website or Create
Website from the StartPage) that is an ASP.NET Website, and a Project
that is created with *the "ASP.NET Application" template?

I see some obvious differences: the Project creates the working folder
under the Visual Studio 2005\Projects directory, while the Website
creates it in the Inetpub\wwwroot directory. And there are some more
subtle differences that I don't understand as well. *The project
creates some .cs (in C#) files for a lot of the things that the
website does not (e.g., in the Website, there is no .cs file generated
for DataSets (.xsd files), and theres no <page>.designer.cs file
generated for pages). *The project uses different namespace
definitions for the same files in the same relative directory
positions. And it seems that some of the web administration tools (the
whole Website menu, including "Copy Web") is missing when you're
working with a project. *Also, it appears (I'm not sure) that the
compiled code for the website is never stored (it seems to be being
regenerated on the fly when I access the website.)

I see these differences, but I don't understand why they're there or
to what purpose they are there. Can someone explain it to me?

Thanks.
Hi

The project form of a web app is similar to the previous version of
visual studio (VS2003) where everything is compiled into a DLL
assembly file. ASP.NET 1.1 could only support "code behind" in this
manner, the alternative being script embedded in the .aspx files.

ASP.NET 2.0 allows code behind files (.cs files) to accompany
the .aspx in the deployed version, whereupon it is compiled "on the
fly" by the web server. The "web site" form of web application in
VS2005 works on the same principle. It has the advantage of being
simpler to deploy and update. In addition to the project folder it can
create a website folder in your documents area instead of using
inetpub/wwwroot (which may not have been installed anyway). In this
mode VS2005 runs its own web server software using a special port
number.

Hope that throws some light on it.
Jun 27 '08 #2
On Apr 17, 6:38 pm, Stan <goo...@philphall.me.ukwrote:
On 17 Apr, 18:41, daveh551 <gee...@gmail.comwrote:
What, from a high level point of view, is the difference (in Visual
Studio 2005) between Website (accessed with Open Website or Create
Website from the StartPage) that is an ASP.NET Website, and a Project
that is created with the "ASP.NET Application" template?
I see some obvious differences: the Project creates the working folder
under the Visual Studio 2005\Projects directory, while the Website
creates it in the Inetpub\wwwroot directory. And there are some more
subtle differences that I don't understand as well. The project
creates some .cs (in C#) files for a lot of the things that the
website does not (e.g., in the Website, there is no .cs file generated
for DataSets (.xsd files), and theres no <page>.designer.cs file
generated for pages). The project uses different namespace
definitions for the same files in the same relative directory
positions. And it seems that some of the web administration tools (the
whole Website menu, including "Copy Web") is missing when you're
working with a project. Also, it appears (I'm not sure) that the
compiled code for the website is never stored (it seems to be being
regenerated on the fly when I access the website.)
I see these differences, but I don't understand why they're there or
to what purpose they are there. Can someone explain it to me?
Thanks.

Hi

The project form of a web app is similar to the previous version of
visual studio (VS2003) where everything is compiled into a DLL
assembly file. ASP.NET 1.1 could only support "code behind" in this
manner, the alternative being script embedded in the .aspx files.

ASP.NET 2.0 allows code behind files (.cs files) to accompany
the .aspx in the deployed version, whereupon it is compiled "on the
fly" by the web server. The "web site" form of web application in
VS2005 works on the same principle. It has the advantage of being
simpler to deploy and update. In addition to the project folder it can
create a website folder in your documents area instead of using
inetpub/wwwroot (which may not have been installed anyway). In this
mode VS2005 runs its own web server software using a special port
number.

Hope that throws some light on it.
Thanks, Stan. That does help some. But I guess it raises the question
of "WHY???" Why would you want to compile something everytime you run
the web application, instead of compiling it and downloading the DLL?
And it seems to expose you to the possibility of more inconsistencies
if your execution environment is different from your development
envirionment. Like right now I'm having fits because it's trying to
compile the .XSD Dataset definition files on the server that I've
deployed to, and immediately cratering (on line 1) for no apparent
reason, but apparently SOMETHING is different about the compiler or
environment that is running on the server compared to what I built
with. If I was deploying the .dll , I wouldn't have that problem.
Jun 27 '08 #3
On 18 Apr, 05:28, daveh551 <gee...@gmail.comwrote:
On Apr 17, 6:38 pm, Stan <goo...@philphall.me.ukwrote:


On 17 Apr, 18:41, daveh551 <gee...@gmail.comwrote:
What, from a high level point of view, is the difference (in Visual
Studio 2005) between Website (accessed with Open Website or Create
Website from the StartPage) that is an ASP.NET Website, and a Project
that is created with *the "ASP.NET Application" template?
I see some obvious differences: the Project creates the working folder
under the Visual Studio 2005\Projects directory, while the Website
creates it in the Inetpub\wwwroot directory. And there are some more
subtle differences that I don't understand as well. *The project
creates some .cs (in C#) files for a lot of the things that the
website does not (e.g., in the Website, there is no .cs file generated
for DataSets (.xsd files), and theres no <page>.designer.cs file
generated for pages). *The project uses different namespace
definitions for the same files in the same relative directory
positions. And it seems that some of the web administration tools (the
whole Website menu, including "Copy Web") is missing when you're
working with a project. *Also, it appears (I'm not sure) that the
compiled code for the website is never stored (it seems to be being
regenerated on the fly when I access the website.)
I see these differences, but I don't understand why they're there or
to what purpose they are there. Can someone explain it to me?
Thanks.
Hi
The project form of a web app is similar to the previous version of
visual studio (VS2003) where everything is compiled into a DLL
assembly file. ASP.NET 1.1 could only support "code behind" in this
manner, the alternative being script embedded in the .aspx files.
ASP.NET 2.0 allows code behind files (.cs files) to accompany
the .aspx in the deployed version, whereupon it is compiled "on the
fly" by the web server. The "web site" form of web application in
VS2005 works on the same principle. It has the advantage of being
simpler to deploy and update. In addition to the project folder it can
create a website folder in your documents area instead of using
inetpub/wwwroot (which may not have been installed anyway). In this
mode VS2005 runs its own web server software using a special port
number.
Hope that throws some light on it.

Thanks, Stan. *That does help some. But I guess it raises the question
of "WHY???" Why would you want to compile something everytime you run
the web application, instead of compiling it and downloading the DLL?
And it seems to expose you to the possibility of more inconsistencies
if your execution environment is different from your development
envirionment. Like right now I'm having fits because it's trying to
compile the .XSD Dataset definition files on the server that I've
deployed to, and immediately cratering (on line 1) for no apparent
reason, but apparently SOMETHING is different about the compiler or
environment that is running on the server compared to what I built
with. *If I was deploying the .dll , I wouldn't have that problem.- Hidequoted text -

- Show quoted text -
The DLL file does not contain code that can be executed directly by
the Server processor. It's an intermediate language that saves time
parsing the source code from scratch. Issues due to compiler version
differences might still arise.

However if you suspect that then try using the option of "publishing"
the web site which will create a DLL out of the .cs and other files.
Jun 27 '08 #4
On Apr 18, 2:56 am, Stan <goo...@philphall.me.ukwrote:
On 18 Apr, 05:28, daveh551 <gee...@gmail.comwrote:
On Apr 17, 6:38 pm, Stan <goo...@philphall.me.ukwrote:
On 17 Apr, 18:41, daveh551 <gee...@gmail.comwrote:
What, from a high level point of view, is the difference (in Visual
Studio 2005) between Website (accessed with Open Website or Create
Website from the StartPage) that is an ASP.NET Website, and a Project
that is created with the "ASP.NET Application" template?
I see some obvious differences: the Project creates the working folder
under the Visual Studio 2005\Projects directory, while the Website
creates it in the Inetpub\wwwroot directory. And there are some more
subtle differences that I don't understand as well. The project
creates some .cs (in C#) files for a lot of the things that the
website does not (e.g., in the Website, there is no .cs file generated
for DataSets (.xsd files), and theres no <page>.designer.cs file
generated for pages). The project uses different namespace
definitions for the same files in the same relative directory
positions. And it seems that some of the web administration tools (the
whole Website menu, including "Copy Web") is missing when you're
working with a project. Also, it appears (I'm not sure) that the
compiled code for the website is never stored (it seems to be being
regenerated on the fly when I access the website.)
I see these differences, but I don't understand why they're there or
to what purpose they are there. Can someone explain it to me?
Thanks.
Hi
The project form of a web app is similar to the previous version of
visual studio (VS2003) where everything is compiled into a DLL
assembly file. ASP.NET 1.1 could only support "code behind" in this
manner, the alternative being script embedded in the .aspx files.
ASP.NET 2.0 allows code behind files (.cs files) to accompany
the .aspx in the deployed version, whereupon it is compiled "on the
fly" by the web server. The "web site" form of web application in
VS2005 works on the same principle. It has the advantage of being
simpler to deploy and update. In addition to the project folder it can
create a website folder in your documents area instead of using
inetpub/wwwroot (which may not have been installed anyway). In this
mode VS2005 runs its own web server software using a special port
number.
Hope that throws some light on it.
Thanks, Stan. That does help some. But I guess it raises the question
of "WHY???" Why would you want to compile something everytime you run
the web application, instead of compiling it and downloading the DLL?
And it seems to expose you to the possibility of more inconsistencies
if your execution environment is different from your development
envirionment. Like right now I'm having fits because it's trying to
compile the .XSD Dataset definition files on the server that I've
deployed to, and immediately cratering (on line 1) for no apparent
reason, but apparently SOMETHING is different about the compiler or
environment that is running on the server compared to what I built
with. If I was deploying the .dll , I wouldn't have that problem.- Hide quoted text -
- Show quoted text -

The DLL file does not contain code that can be executed directly by
the Server processor. It's an intermediate language that saves time
parsing the source code from scratch. Issues due to compiler version
differences might still arise.

However if you suspect that then try using the option of "publishing"
the web site which will create a DLL out of the .cs and other files.
THANK YOU, Thank you, thank you, Stan. Publishing solved my parser
error problem. And MOST everything seems to be working now EXCEPT for
one critical thing. My login page (which, of course, is critical to
the guts of the site!) blows up with this error:

Compilation Error
Description: An error occurred during the compilation of a resource
required to service this request. Please review the following specific
error details and modify your source code appropriately.

Compiler Error Message: CS0030: Cannot convert type 'ASP.login_aspx'
to 'System.Web.UI.WebControls.Login'

Source Error:

[No relevant source lines]
Here is the .aspx file for that page:

<%@ page language="C#" masterpagefile="~/TakeCharge.master"
autoeventwireup="true" inherits="Login, App_Web_8mstyslz"
title="Login" %>
<asp:Content ID="Content1" ContentPlaceHolderID="MainContent"
Runat="Server">
<h1>Login now to create, revise, or view your plan.
</h1<asp:Login ID="Login1" runat="server"
OnLoggedIn="Login_LoggedIn">
</asp:Login>
<br />

[followed by some text and links]

Once again, it runs fine in development, and it runs fine when moved
over to my Win 2000 Server machine. I haven't a clue as to what's
wrong.

If it will help, feel free to visit the site and look at the error
output. It put out a couple hundred lines of compiler source, which I
didn't think it was worthwhile to copy in here. The site is
www.takechargeofyourdebts.com, and the CustomErrors is turned off (as
of 4/18/2008 - I obviously won't leave it that way once I get this
resolved.)

Thanks for your help.

Jun 27 '08 #5
On Apr 18, 2:56 am, Stan <goo...@philphall.me.ukwrote:
On 18 Apr, 05:28, daveh551 <gee...@gmail.comwrote:
On Apr 17, 6:38 pm, Stan <goo...@philphall.me.ukwrote:
On 17 Apr, 18:41, daveh551 <gee...@gmail.comwrote:
What, from a high level point of view, is the difference (in Visual
Studio 2005) between Website (accessed with Open Website or Create
Website from the StartPage) that is an ASP.NET Website, and a Project
that is created with the "ASP.NET Application" template?
I see some obvious differences: the Project creates the working folder
under the Visual Studio 2005\Projects directory, while the Website
creates it in the Inetpub\wwwroot directory. And there are some more
subtle differences that I don't understand as well. The project
creates some .cs (in C#) files for a lot of the things that the
website does not (e.g., in the Website, there is no .cs file generated
for DataSets (.xsd files), and theres no <page>.designer.cs file
generated for pages). The project uses different namespace
definitions for the same files in the same relative directory
positions. And it seems that some of the web administration tools (the
whole Website menu, including "Copy Web") is missing when you're
working with a project. Also, it appears (I'm not sure) that the
compiled code for the website is never stored (it seems to be being
regenerated on the fly when I access the website.)
I see these differences, but I don't understand why they're there or
to what purpose they are there. Can someone explain it to me?
Thanks.
Hi
The project form of a web app is similar to the previous version of
visual studio (VS2003) where everything is compiled into a DLL
assembly file. ASP.NET 1.1 could only support "code behind" in this
manner, the alternative being script embedded in the .aspx files.
ASP.NET 2.0 allows code behind files (.cs files) to accompany
the .aspx in the deployed version, whereupon it is compiled "on the
fly" by the web server. The "web site" form of web application in
VS2005 works on the same principle. It has the advantage of being
simpler to deploy and update. In addition to the project folder it can
create a website folder in your documents area instead of using
inetpub/wwwroot (which may not have been installed anyway). In this
mode VS2005 runs its own web server software using a special port
number.
Hope that throws some light on it.
Thanks, Stan. That does help some. But I guess it raises the question
of "WHY???" Why would you want to compile something everytime you run
the web application, instead of compiling it and downloading the DLL?
And it seems to expose you to the possibility of more inconsistencies
if your execution environment is different from your development
envirionment. Like right now I'm having fits because it's trying to
compile the .XSD Dataset definition files on the server that I've
deployed to, and immediately cratering (on line 1) for no apparent
reason, but apparently SOMETHING is different about the compiler or
environment that is running on the server compared to what I built
with. If I was deploying the .dll , I wouldn't have that problem.- Hide quoted text -
- Show quoted text -

The DLL file does not contain code that can be executed directly by
the Server processor. It's an intermediate language that saves time
parsing the source code from scratch. Issues due to compiler version
differences might still arise.

However if you suspect that then try using the option of "publishing"
the web site which will create a DLL out of the .cs and other files.
Stan, I thought I had replied already thanking you for your help.
Publishing gets me over the hurdle of the parser error in the XSD
file. It generated a strange compilation error though. The login
page bombed out, saying it couldn't convert type ASP.login_aspx to
System.Web.UI.Controls.Login. I don't get that error when I run (even
the precompiled version) on my local server, but I figured out that it
seems to have to do with having a page named (and therefore a class
named) the same as one of the controls, namely Login (the page) and
Login (the control). This is rather strange since it's my
understanding that "Login.aspx" is the default and accepted name for
the login page used by forms authentication. But I was able to work
around it by creating a new page called "LoginPage.aspx", and
redirecting the forms authentication there.

Now it's just getting a security exception when it (apparently) tries
to open the Config file, but we're getting way outside the original
scope of this thread.

Again, thank you for your help.
Jun 27 '08 #6

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

2
by: js | last post by:
I am using Visual Studio 2003. An IIS is installed on a separate box with the Remote Debugger server component from VS2003. Initially, I created a new blank project in VS2003 under the IIS's...
2
by: Rob Dob | last post by:
Hi, How do I go about installing another Web Site Project inside my existing VS2005 website project. I currently have both a forum WSP and my main WSP application within the same solution. Both...
13
by: Kobee | last post by:
Hi, I'm having a few issues adapting to new 2.0 "website" project vs. the old 1.1 "web application". One of the major issues I'm having is with the notion of namespaces. Using the old way, I...
3
by: mrajanikrishna | last post by:
Hi friends, I've designed an application in my local system using VS.NET 2003. (VB.NET and ASP.NET) Its working fine. Now, I want to publish to my ISPs server. I've FTP account. How can I...
10
by: TS | last post by:
i just noticed the website i created in VS 2005 is running on a different port than the default. I see that it is running on the local web server, and also that the website i created isn't in IIS....
2
by: CodeMonkey | last post by:
Hi all I created a web site project using Visual Studio 2005 and then created the Deployment Project to deploy it. I set the virtual directory property on the web application folder to "testsite"....
1
by: bharathreddy | last post by:
This Article gives an introduction to VSTS Team Foundation & fundamental difference between Visual Source Safe (VSS) and VSTS Team Foundation. Team Foundation is a set of tools and technologies...
3
by: moondaddy | last post by:
What's the preferred (best) way to start a website project in VS 2005? I know of 2 ways and each creates a site differently and has different behavior. Open VS 2005 1) from the start page...
1
ssnaik84
by: ssnaik84 | last post by:
Probably a very basic question.. :) 1) what is difference between ASP.NET website and web application project? 2) ..and if I want to create n-tier architecture for my website.. then which...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: Vimpel783 | last post by:
Hello! Guys, I found this code on the Internet, but I need to modify it a little. It works well, the problem is this: Data is sent from only one cell, in this case B5, but it is necessary that data...
0
by: jfyes | last post by:
As a hardware engineer, after seeing that CEIWEI recently released a new tool for Modbus RTU Over TCP/UDP filtering and monitoring, I actively went to its official website to take a look. It turned...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
1
by: PapaRatzi | last post by:
Hello, I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...
1
by: CloudSolutions | last post by:
Introduction: For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
1
by: Defcon1945 | last post by:
I'm trying to learn Python using Pycharm but import shutil doesn't work
1
by: Shællîpôpï 09 | last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
0
by: af34tf | last post by:
Hi Guys, I have a domain whose name is BytesLimited.com, and I want to sell it. Does anyone know about platforms that allow me to list my domain in auction for free. Thank you

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.