With the release of DNN Platform 8 last week it is now possible to develop modules using SPA and MVC patterns within the DNN platform. As Part of the buildup of the DNN 8 release, Will Strohl provided a Pull request to my DNN Extension Project Templates project to help clean up some of the basic module templates to work better on Windows Azure environments, and to prep them for inclusion of new DNN 8 specific templates for SPA and MVC modules.
Early in the fall Joe Brinkman provided a partial SPA project, with the intention of it becoming a project template. I had a little time when it was initially submitted to work on it, but wasn’t able to get everything squared away on the template until early December. It wasn’t until last week that I got additional time to do further testing on the template and fix a few issues that occurred during the conversion to a project template.
On January 10th, I released the first iteration of the DNN8 project templates for Visual Studio 2015, this release included Will Strohl’s changes, my original templates, and the SPA template with fixes and customizations on what Joe Brinkman had provided. Later that week (Friday night to be exact) I went through the process of integrating the MIT licensed MVC template that Joe Brinkman had also created. I put this through a few rounds of testing, fixes, and released that on January 15.
As of now, the release is marked as a Beta on GitHub, but I would say that this is the one you should start with. As always if you have any feedback or questions, please let me know!
With the release of DNN8 I put together a couple of quick video tutorials, with more coming in the next few weeks.
The first video is a DNN8 Installation Video, this video shows you how to setup DNN8 in a local development environment using the local DNNDEV.ME url, this URL is embedded in the project templates, so if you want to use the templates it is suggested that you setup DNN in this way.
The second video tutorial is a video on how to find and install the Project templates using the Visual Studio Gallery.
Where to Create the Project
The SPA template follows the same approach as all of the other module templates in the collection, you create the Module project under the /desktopmodules/ folder. The MVC template is a little different, this project should be created in the /desktopmodules/mvc/ folder, this is important as the PATH for the references and the build path for the DLL is setup for this, if you put the module elsewhere, it likely will not build, and will not work.
One thing to keep in mind with the project templates in Visual Studio, occasionally VS will freak out upon project creation, and in IIS will turn the DesktopModules folder into a “virtual directory”, this causes the DNN website to fail to load. If the site fails to load for you after creating a project from these templates, to into the IIS Manager, expand the website, and see if there is a little “arrow” on the DesktopModules folder, if so, right click on it and choose delete. This should resolve the problem.
DNNCorp Project Templates
During the time it took me to get all the kinks worked out on the code that Joe submitted, DNN Corp decided that they would manage and release their own templates. Competition typically makes things better right? We shall see, my experience with Corp managing templates in the past was poor, they never bothered to do anything with them, thus the reason I started maintain templates myself. If they can maintain them it will be a good thing for the community, but I have been maintaining DNN templates for going on 6+ years now, and know how I like them, and how best to work within a very well defined and specific development process, so I will continue to develop and maintain my templates, and create tutorials for them.