Peter Donker raised the question in the DNN Connect Facebook Group – “How can you access the Client Resource Manager in an MVC View?”. I gave him the answer as a reply but I thought it would be good to provide a more accessible source for the information.
I have called it “Classic Webforms” as it primarily uses features of DNN that were available prior to version 5, when we began to add additional ways to develop modules. However, as with most of my example modules this module is developed using a number of modern “Best Practices” – these Best Practices are highlighted in italic.
When I announced that I was no longer working at DNN Corp, I did make it clear that it was still my intention to remain active in the DNN Community. And so, for the last couple of weeks I have been trying to decide what I should do.
In my role as Senior Architect and Chief Architect at DNN Corp I often found myself adding or updating the framework for developers to write module extensions for DNN. And, of course, that meant that I needed to create a module in order to test out those features. Often I did this by creating a To-do or Task List module.
DNN 8 will support creating modules using ASP.NET MVC version 5.1 or later. In previous blogs in this series I showed how you can set up your environment to create MVC modules and I created my first MVC Action/View. In this blog I will describe the support we have included for localizing text in MVC Controllers and MVC Views. As before the source code for my examples is available on Github at https://github.com/cnurse/DnnConnect.Demo.
In my previous blog I reviewed the Development Environment I will be using for my blog series on Module Development in DNN 8. As a reminder you can find all the sample code on Github at https://github.com/cnurse/DnnConnect.Demo. In this blog we will create our first MVC Action and View.
A new CTP for DNN 8 was released this week. This CTP contains updated support for building modules using the ASP.NET MVC Framework as well as new support for building HTML 5 based modules. This adds to the existing support for building modules with ASP.NET WebForms (User Controls) and Razor scripts.
Last summer DNN Corp announced their intention to support MVC in future versions of the eponymous DNN Platform.
Last week Joe Brinkman announced that the initial fruits of those labours was now available in a CTP of DNN 7.5. The support introduced in 7.5 will allow developers to build their DNN modules using ASP.NET MVC version 5.1.1 or later.