Last post Aug 23, 2011 09:43 AM by atconway
Aug 20, 2011 02:00 AM|Mayil_Gilli|LINK
I would like to build a service oriented SAAS application in asp.net. it has two types of apps one is website and another one is web application .
1. which one is best for saas apps.
2. What is difference between website and web application?
3. Whisch application has more advantages and best?
Aug 20, 2011 02:06 AM|amitpatel.it|LINK
Web application they are basicaly project specific single assebly (ddl ) in bin folder. while in web site they are dll for page wise.
In App_Code related class file no need to compile application in web site jsut need to chagen and update in server without build they are run as inline code. But that is not like that in web application.
Suggested approach for SAAS is web application.
Aug 23, 2011 09:43 AM|atconway|LINK
I guess it depends on the size of project and your developement needs that will answer that question best. With that said the 1st words out of my mouth when asked that will almost always be 'Web Application'.
A few years back when I 1st started using VS.NET 2005 and that project template became available, I started out by making 'website' projects. I quickly found how much was stripped out of the Development IDE as far as configuration and settings that made
it difficult. One of my biggest complaints was in the way the websites are deployed. All of the code files are deployed to the server and compiled at runtime with a 'website', as opposed to a web application is precompiled into a .dll that will be deployed
to the /bin. This offers ability too to use Reflection to get information about the compiled .dll (versioning, etc) to display within the app if needed (not typically a huge need, but nice to have).
In my opinion, it always seemed to me that the 'website' project template was designed more for the novice or 'get it up quick and running' developer where security and large project needs were not required. While I have not obviously seen that in writing,
it appears to be a good fit for that template based on the restrictions and filtering of lower level design that is available. It to me is analgous to using a SqlDataSource where all of the connection info is stored in the UI code in the control vs using
a full blown multi-layered design where that info is relagated to the DAL.
Both work, it is just which fits the project better.
Web application projects with thier compiled .dlls also offer a preformance benefit (for very large sites only) by having the code pre-compiled where the website project will be compiled at runtime.
IMO... go with the Web Application project.
Here is a really good MSDN article to highlight the differences as well:
Web Application Projects versus Web Site Projects:
If you already made a 'Web Site' and want to convert it to a 'Web Application', please refer to the following link:
Walkthrough: Converting a Web Site Project to a Web Application Project in Visual Studio:
Hope this helps!