1

I want to learn the pros and cons of using Web Site project type or using ASP.Net Web Application Project type?

My web application is using ASP.Net 2.0 or later, and the web application just shows UI, call some other database store procedure and some other WCF Web Services.

thanks in advance, George

Improve this question
1

1 Answer 1

Reset to default
3

The Web Site project was an attempt by Microsoft to make it as simple as possible to develop and deploy an ASP.NET application, seemingly in an attempt to compete with simpler frameworks such as Ruby on Rails. The Web Site project does not use a csproj file to control references, project settings, etc., it relies on the directory and file structure of the project.

In my experience, the lack of a proj file creates more headaches than it solves. I would definitely stick with Web Application Projects.

Here are a few references:

http://www.techbubbles.com/aspnet/aspnet-website-vs-web-application-project/

http://blogs.microsoft.co.il/blogs/maordavid/archive/2007/06/03/ASP.NET-2.0-2D00-Web-Site-vs-Web-Application-project.aspx

Improve this answer
Sign up to request clarification or add additional context in comments.

3 Comments

A further question, I did not find any cons of using web site? Any comments?
I think the biggest issue I've seen is with Source Control. Since there is no proj file to manage references, you're sort of forced to put your DLLs/binaries under source control, which can be annoying, and possibly considered bad practice.
Despite what I've said, it partly comes down to personal preference. You should try a few projects using both methodologies and decide which one works better for you.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.