What is The Difference Between Web Application and Web Site

Question

What is The Difference Between Web Application and Web Site ???

Brajesh Kumar · Answer

This is totally personal and subjective but I'd say that a website is defined by its content while a web application is defined by its interaction with the user . That is a website can plausibly consist of a static content repository that's dealt out to all visitors while a web application depends on interaction and requires programmatic user input and data processing. For example A news site would be a website but a spreadsheet or a collaborative calendar would be web applications. The news site shows essentially the same information to all visitors  while the calendar processes individual data. Practically most websites with quickly changing content will also rely on a sophisticated programmatic (and/or database) backend but at least in principle they're only defined by their output. The web application on the other hand is essentially a program that runs remotely and it depends fundamentally on a processing and a data storage backend.

Anil Jha · Answer

Web application will have one common dll named as project name but web site will have multiple dll folder wise.

Pradeep Yadav · Answer

A website can consist of a static content repository that's dealt out to all visitors while a web application depends on interaction and requires programmatic user input and data processing.

Gokhul Varman · Answer

It has some basic differences for more explanation refer the link:http://www.seguetech.com/website-vs-web-application-whats-the-difference/

Rajeesh Menoth · Answer

Web Application Projects : You want to be able to use the Edit and Continue feature of the Visual Studio debugger. You want to run unit tests on code that is in the class files that are associated with ASP.NET pages. You want to refer to the classes that are associated with pages and user controls from standalone classes. You want to establish project dependencies between multiple web projects. You want the compiler to create a single assembly for the entire site. You want control over the assembly name and version number that is generated for the site. You want to use MSBuild or Team Build to compile the project. For example you might want to add prebuild and postbuild steps. You want to avoid putting source code on a production server. Web Site Projects : You want to include both C# and Visual Basic code in a single web project. (By default a web application is compiled based on language settings in the project file. Exceptions can be made but it is relatively difficult.) You want to open the production site in Visual Studio and update it in real time by using FTP. You do not want to have to explicitly compile the project in order to deploy it. If you do precompile the site you want the compiler to create multiple assemblies for the site which can include one assembly per page or user control or one or more assemblies per folder. You want to be able to update individual files in production by just copying new versions to the production server or by editing the files directly on the production server. If you precompile the site you want to be able to update individual ASP.NET web pages (.aspx files) without having to recompile the entire site. You like to keep your source code on the production server because it can serve as an additional backup copy. Reference : https://msdn.microsoft.com/en-us/library/dd547590(v=vs.110).aspx http://www.seguetech.com/blog/graphic/2013/04/16/website-vs-web-application-difference

Munesh Sharma · Answer

http://www.seguetech.com/blog/graphic/2013/04/16/website-vs-web-application-difference

Vivek Kumar · Answer

Hi Please go through the below link for your reference. http://www.aspdotnet-suresh.com/2012/10/aspnet-difference-between-website-and.html --------------------------------------------------- If this post helps you mark it as answer