Hi,
can someone explain the difference between the 2?
Loading
Know the answer? Post it — somebody with the same question will find it here.
Sign in to answer this question
It is the same account you read, post and publish with — and you will come straight back to this page.
TulasiPosted Nov 17, 2011, 2:11 AM
Web Site
1. We can code one page in C# and one page in vb.net (Multiple programming languages allowed).
2. We cannot call (access) public functions from one page to other page.
3. Utility classes / functions must be placed in a special ASP.NET folder (the App_Code folder)
4. Web Sites do not have a .csproj/.vbproj file that manages the project (the folder that contains the site becomes the project root).
5. In the Web Site project, each file that you exclude is renamed with an exclude
keyword in the filename.
6. Explicit namespaces are not added to pages, controls, and classes by default, but you can add them manually.
Web Application
1. Only one programming language allowed per project (Need to decide on programming language when starting project).
2. We can access public functions from one page to other page.
3. Utility classes / function can be placed anywhere in the applications folder structure.
4. Web Applications are treated like other .NET projects and are managed by a project file (.csproj or .vbproj) .
5. One nice feature of the Web Application project is it's much easier to exclude files from the project view.
6. Explicit namespaces are added to pages, controls, and classes by default.
• Deployment wise difference
Web Site
1. It has its code in a special App_Code directory and it's compiled into several DLLs (assemblies) at runtime.
2. No need to recompile the site before deployment.
3. We need to deploy both .aspx file and code behind file.
4. Small changes to the site do not require a full re-deployment. (We can upload the code file that was changed)
Web Application
1. web application is precompiled into one single DLL.
2. Site has to be pre-compiled before deployment .
3. Deploy only .aspx page, but not associated code file (the pre-compiled dll will be uploaded) .
4. Even small changes require a full re-compile of the entire site(i.e. if the code for a single page changes the whole site must be compiled) (It requires careful planning to ensure new bugs aren't introduced to the production site when uploading bug fixes or other changes.)
If it helps you, do not forget to mark it as accepted.
Prabhu RajaPosted Nov 17, 2011, 2:01 AM
Web Application
On top of the hierarchy is the web application. In technical terms, this is a web site in IIS (with an associated application pool). A default web site listens for incoming HTTP requests on port number 80. But we can create additional web sites, having different port numbers or IP addresses. We can configure each IIS web application independently. We can have one web application configured in anonymous access one in integrated authentication etc.
Site
Site is a collection of web pages which is used to store information in an organized way. Site stores list of documents, discussion, events, task and many other types of information. Site provides controlled access to share information among user; i.e. only authorized users are allowed to access shared information. You can have multiple sites under each site collection; each site can have multiple sub sites also.
Check out this Article : http://www.c-sharpcorner.com/uploadfile/Roji.Joy/difference-between-web-application-site-collection-and-site/
Manoj SevdaPosted Nov 17, 2011, 1:12 AM
A web application serves a specific function such a shopping cart or a blogging application.
So a web site can have a message board, a blog, a photo gallery and many other types of web applications under it's cloud.
Definition of Web Application
WEB APPLICATION
An application that is delivered using Internet technology and meets one or more of the following conditions:
Utilizes a database (such as Oracle or SQL Server)
Is developed using an application development tool (such as Oracle Internet Developer Suite or Visual Studio)
Extracts data from multi-record files
Requires a constantly running server process (such as Newsgroups and Chatrooms)
Stores input data from data entry screens or web forms
Depending on its requirements, a web application may be an Internet Application or an Intranet Application.
Definition of Website
WEBSITE
The entire collection of web pages and other information (such as images, sound, and video files, etc.) that are made available through what appears to users as a single web server
Read more: http://wiki.answers.com/Q/What_is_the_difference_between_a_website_and_a_web_application#ixzz1dwMtQG7d
Datta KharadPosted Nov 17, 2011, 12:43 AM
Refer this link..
http://www.c-sharpcorner.com/Forums/Thread/143937/what-is-the-basic-difference-between-the-web-site-and-we.aspx
Kunal NaikPosted Nov 16, 2011, 1:15 AM
One of the key differences is that Websites compile dynamicly and create on the fly assemblies, while web applicaitons compile into one large assembly. See also following link,
Click Here
AartiPosted Nov 16, 2011, 1:03 AM
Datta KharadPosted Nov 16, 2011, 1:02 AM
Difference between web application and web site
A common question by asp.net developers is what project model should I use for asp.net application? Web Site project (which introduced with VS 2005) or Web Application project (which delivered as add-in for VS 2005 and built-in within VS 2005 SP1)?There is no thumb rule. Every project model has it's own advantages (and diss-advantages off course...). I hope this post will help you to understand better the differences between 2 of them.
Web Application project model
Provides the same Web project semantics as Visual Studio .NET 2003 Web projects.
Has a project file (structure based on project files).
Build model - all code in the project is compiled into a single assembly.
Supports both IIS and the built-in ASP.NET Development Server.
Supports all the features of Visual Studio 2005 (refactoring, generics, etc.) and of ASP.NET 2.0 (master pages, membership and login, site navigation, themes, etc).
Using FrontPage Server Extensions (FPSE) are no longer a requirement.
Web Site project model
No project file (Based on file system).
New compilation model. (Read here or here for more details) and ...
Dynamic compilation and working on pages without building entire site on each page view.
Supports both IIS and the built-in ASP.NET Development Server.
Each page has it's own assembly.
Defferent code model. (Read here for more details)
Ok, all is great, but you want to create your web site now. Which model should you use?
You need to migrate large Visual Studio .NET 2003 applications to VS 2005? use the Web Application project.
You want to open and edit any directory as a Web project without creating a project file? use Web Site project.
You need to add pre-build and post-build steps during compilation? use Web Application project.
You need to build a Web application using multiple Web projects? use Web Application project.
You want to generate one assembly for each page? use Web Site project.
You prefer dynamic compilation and working on pages without building entire site on each page view? use Web Site project.
You prefer single-page code model to code-behind model? use Web Site project.
You can refer these links...
http://msdn.microsoft.com/en-us/library/aa730880(v=vs.80).aspx
--------------------------------------
http://msdn.microsoft.com/en-us/library/aa730880%28VS.80%29.aspx#wapp_topic5
--------------------------
http://blogs.msdn.com/b/aspnetue/archive/2009/12/14/asp-net-web-application-projects-vs-web-site-projects-in-visual-studio.aspx
Please mark as Accepted answer if your query resolved.
Priya LingePosted Nov 16, 2011, 12:58 AM
Please check below link which explain the diff between these two.
http://www.dotnetspider.com/resources/1520-Difference-between-web-site-web-application.aspx
Hope this will help you.
Thanks.