Installation and deployment
Version 7.x > Installation and deployment > Web Application vs. Web Site View modes: 
User avatar
Member
Member
Ken Sykora - 9/27/2012 3:53:44 PM
   
Web Application vs. Web Site
Hi everyone -- just new to Kentico and question about best practices for development here.

The installer recommends using a Web Site versus a Web Application. Typically I've found that web apps are much more preferred because you get a full build and more accurate errors and building is quicker, but what I'm finding with Kentico is that the site itself takes a very long time to build in visual studio as a web app (up to a minute)

I tried removing most of the core CMS ASPX files but they seem to be needed by the application to run on the site (I wish a DLL with the compiled ASPXs was shipped separately) so unfortunately excluding files seems to be out of the question here. Coming from a Sitecore background, this is typically our workflow but it doesn't seem to work with Kentico.

So, my overall question is, why is the website marked as the recommended option here? What's the best/quickest way to do development using visual studio to minimize build times? Any good blog posts on getting started and best practices? I'm trying to dive in head first and I'm a very fast learner so throw 'em at me.

Thanks!

User avatar
Kentico Legend
Kentico Legend
Brenden Kehren - 9/27/2012 10:25:46 PM
   
RE:Web Application vs. Web Site
Great points Ken! Kentico is very flexible when it comes to development, which is why there are so many aspx and acsx pages in the project. The website is recommended because you can extend so much of the UI (CMSDesk, CMSSiteManager, webparts, modules, etc.). Here is a simple example, I wanted to allow a specific role to be able to "log in" as a user. Typically this is only available to administrators, but I was able to modify the code behind with ease to allow for this to happen. Just like developing a web app vs. a website, you can easily update a website without the need to recompile down to a .dll everytime a simple update is made.

Also, depending on how much custom code you will be doing, I'm willing to bet, once you see how Kentico works and how easy development is done from the UI, you will very rarely need Visual Studio to do anything. The UI is very powerful!

I'd suggest checking out the Videos section of the DevNet, Thomas Robbins has a great set of videos there for one to get a jump start. Granted they are for v6 but it will at least help to you get an idea of how things work.

Good luck!