This varies a bit from the MSDN Documentation walkthrough on moving an ASP.Net Web Site Project to a Web Application Project as there are some added steps due to several reasons in the architecture of BlogEngine.Net e.g. the way BlogEngine does themes, its widgets framework and controls dependencies. These are not to criticise the design decisions made, it still is a full featured, well built blogging application which I use and customise daily.
Here are the steps repeated, but I encourage anyone benefitting from this to post your thanks to Ben on this thread as well so that he knows.
1. Create a new WAP. File -> New -> Project -> Visual C# -> ASP.NET Web Application. Select the location (I created a new folder for this WAP project), and I used ‘BeWap’ for the Name of the project.
2. Close Solution.
3. In Windows Explorer, copy all the BE files into the WAP folder. You’ll be overwriting a couple of the files that were included in the new WAP project we created (default.aspx and web.config and maybe a couple of others).
4. Rename the App_Code folder to Old_App_Code.
5. Reopen WAP solution in Visual Studio.
6. Right-click on project name (BeWap) in Solution Explorer, and select ‘Add Reference’. Go to the Browse tab, and browse to the BIN directory in this project, select ‘BlogEngine.Core.dll’.
7. In Solution Explorer, click the ‘Show All Files’ icon. All the files/folders that we copied into the WAP folder will show up in Solution Explorer, but they are not yet included in the project, so they are white/ghosted out icons. Select all these ‘excluded’ folders/files in Solution Explorer, right-click and select ‘Include in Project’.
8. Select the top node in Solution Explorer, ‘BeWap’ (right under Solution ‘BeWap’). Right-click and select ‘Convert to Web Application’.
9. Save all files (Ctrl-Shift-S).
10. In the web.config file, in the <pages> section, there’s this line:
<add namespace=”Controls” tagPrefix=”blog”/>
Change that to:
<add assembly=”BeWap” namespace=”Controls” tagPrefix=”blog”/>
… where “BeWap” is the name of this WAP project.
11. The site.master files for Indigo, Mobile and Standard all have the same class name of ‘site’. Change the class name in site.master.cs for the Standard theme to site_standard and changed the Inherits attribute in the <%@ Master %> directive in site.master to site_standard (so they match). Need to do the same thing for the Indigo and Mobile themes … giving them class names of site_indigo and site_mobile.
12. The class name in edit.ascx, edit.ascx.cs and edit.ascx.designer.cs files in the RecentComments widget is widgets_RecentPosts_edit. Need to change the class name in these 3 files to widgets_RecentComments_edit.
13. The class name in edit.ascx, edit.ascx.cs and edit.ascx.designer.cs files in the TextBox widget is widgets_LinkList_edit. Need to change the class name in these 3 files to widgets_TextBox_edit.
14. The class name in widget.ascx, widget.ascx.cs and widget.ascx.designer.cs files in the TextBox widget is widgets_LinkList_widget. Need to change the class name in these 3 files to widgets_TextBox_widget.
15. Save all files (Ctrl-Shift-S).
16. When trying to build the project, I was getting about 47 errors about unrecognized controls. The problem was the ‘designer.cs’ files didn’t get created for these ASPX pages back in step 8 when I did the ‘Convert to Web Application’ command. Even if I try repeating that step again, the designer.cs files still do not get created. Visual Studio is complaining that various BE controls (blog:SearchBox, blog:PageList, etc) are unknown server tags. If Visual Studio can build the project once, then these BE controls will start to get recognized. What I did to get this done was temporarily exclude these pages that reference the BE controls. The pages referencing these controls can be found in Visual Studio’s error list when you try to build the project. I excluded the entire Widgets folder, the entire themes folder, the post.aspx file, the error404.aspx file, the default.aspx file and the apiTagMiniView.aspx file.
17. Build the solution. Should get no errors.
18. Add those temporarily excluded items back into the project from two steps ago.
19. Select the top node in Solution Explorer, ‘BeWap’ (right under Solution ‘BeWap’). Right-click and select ‘Convert to Web Application’. The pages we re-included back into the project should now all have designer.cs files.
20. Build the solution. Should get no errors.
21. Run the solution. Everything should work.