For BE going to the web application model in the long run is the best way to go.
For web developers that already use Visual Studio to edit and update their website there is really no changes made there.
Instead of FTPing all of your codebehinds and etc you just FTP your BlogEngine.NET.dll file.
Going with web application as long you are working with the full source code there won't be any lost in terms of being able to update your website or extensions.
The only additional step would be to Rebuild your website Right click on Solution Explorer --> Rebuild and that is it.
That takes any changes you made with codebehinds for extensions or stand alone webpages or master pages and combines all of that into one file.
That is the BlogEngine.NET.dll file
So in general terms in updating your website nothing would really be lost.
Only thing you won't be able to do any more is FTP your codebehind files to the server.
Which now is really a bad practice really in terms of security.
Leaving source code in the open on your server is not good.
Hackers can hack your FTP login info (Not hard to do) and upload all kinds of scripts into your codebehinds.
With Web application with all of your source code compiled into one file BlogEngine.NET.dll makes
less files on server this reducing this security risk.
The problem I can see with the Web Application model would be for those that don't work with Visual Studio or the source code version of BE.
For those they would have to learn how to use Visual Studio with BE which is not hard.
I think for future releases of BE should go with Web Application model and with Custom Fields believe will help reduce the amount of
actual coding to make common changes to BE to make it work.
I am seeing other people and myself included making source code changes to work around or add functionally to make BE work better.
If those functions were already included the source code changes would not be needed.
So point is in exchange in moving to the Web Application model for BE.
The BlogEngine.net platform has to be more flexible in terms of customization
that does not require source code changes in order to do it.
Should all be able to do it from with in the Admin panel.
So Rtur and other BE developers you have alot of work cut out for you :) .
So my vote is YES for Web Application model for BlogEngine.Net
In terms of technology and the future moving to Web Application is really not a true choice.
It is a matter of "When" and not "If" when Microsoft will discontinue support for Web Projects.
So at our current time period it is best to go ahead and get ready for that change.
When you weigh all of the Pros Vs. Con Web Application wins.
Now comes the really sad part for me :(
The next one to go is Web Forms.
MVC is starting to kick up even more speed and support from Microsoft.
Even with Microsoft New One Asp.Net concept
It still sides more with MVC and C# than it does Web Form and VisualBasic.
Go look at http://asp.net
You see tutorials and content for MVC are updated and current.
Look at Web Forums most had not been updated since 2010.
Looking at Microsoft Certification exams all for MVC no WebForms.
So I see in about 2-3 years WebForms support will also go away.
But, for now just need to move to Web Application model.
I see may be BE 3.5 or BE 4.0 being Pure MVC.
If anyone needs any help or questions about Web Project vs Web Application model let me know.
My vote is YES for Web Application model for BlogEngine.Net