For example, with a web application;
■ You can create an MVC application.
■ Visual Studio stores the list of files in a project file (.csproj or .vbproj), rather than
relying on the folder structure.
■ You cannot mix Visual Basic and C#.
■ You cannot edit code without stopping a debugging session.
■ You can establish dependencies between multiple web projects.
■ You must compile the application before deployment, which prevents you from testing
a page if another page will not compile.
■ You do not have to store the source code on the server.
■ You can control the assembly name and version.
■ You cannot edit individual files after deployment without recompiling.
Note:
Typically, website projects are the right choice when one developer will be creating and
managing a website.
Web application projects are better for enterprise environments with multiple developers and formal processes for testing, deployment, and administration.
