Get the hottest modules, skins, and goodies!
Contact us and we'll be happy to assist you.
Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact firstname.lastname@example.org.
Just over six weeks ago Shaun published a blog called “DNN Labs: Project MaVeriCk”, where he indicated that we had initiated a project to look at supporting ASP.NET MVC development in DNN. I have spent about 25% of my time over the last six weeks on this project. There are really two objectives to Project MaVeriCK:
You may have ready my article on the death of ASP.net WebForms. Along came MVC to provide a new solution.
I'll explain why ASP.net MVC started well but was overtaken by the internet, and why the resulting good solution is still called MVC, even though it's not Model-View-Controller. Our goal is to focus our time and energy on the relevant parts and ignore the rest.
As you might have heard, you have to migrate to Razor soon. Old-school developers have a hard time understanding why WebForms should be replaced, since it's worked to well for more than 10 years. So in this part 3 of my Series The Future of DNN Speaks Razor, I'll explain why WebForms turned out to be the wrong solution for web development and how the web changed to make WebForms' strengths obsolete.
As you might have heard, you have to migrate to Razor sooner than later, and the earlier you start, the more you will be creating future-compatible material today. This is part 2 of the Series The Future of DNN Speaks Razor. In this post I'll explain what Razor is, why it's not MVC (even though Razor is popular there as well) and more.
One of the great aspects of being an Open Source platform is that we have an entire community of people who love helping their fellow community members. This is one of the aspects of DNN that has attracted a lot of people to the platform and the community over the last decade. One of the best ways to help others is by sharing your knowledge of DNN, ASP.Net and even Microsoft Azure. Imagine how awesome it would be to help educate other community members while also getting to spend some time at a warm Florida beach in the middle of Winter. Instead of shoveling the sidewalk, you could be relaxing in the sun.
If you could add one feature to DNN what would it be? What bug is at the top of your wish list that you would like to get fixed in the next release? Is there some documentation you would like to see improved? Do you ever wonder why certain decisions are made for the platform or the community? What if I said that you can add that feature, or get that bug fixed, or help improve the documentation?
Over the last 2 weeks I have had a chance to speak to a lot of community members. I heard over and over again that people want to have more visibility into what is happening with the project. People want to help in developing the platform. People want to get involved to help solve many of the community and platform problems, both big and little. In short people want to participate in the development and management of the platform and community.
This is part 1 of the Series The Future of DNN Speaks Razor. In this post I'll explain why you have to migrate now.
DNN (formerly DotNetNuke) provides a suite of solutions for creating rich, rewarding online experiences for customers, partners and employees. DNN products and technology are the foundation for 750,000+ websites worldwide. In addition to our commercial CMS and social community solutions, DNN is the steward of the DotNetNuke Open Source Project.