Let’s Build a Module #4–Data!</h1> <article> <h1>Let’s Build a Module #4–Data!</h1> <p>steve.fabian@dotnetnuke.com — Thu, 02 Feb 2012 20:26:29 GMT</p> <p>In this next part of the series, we’ll take a look at how the combination of Entity Framework and WCF Data Services gives you an awesome data access layer in no time flat, Quick, Easy and Powerful.</p> </article> <article> <h1>Security bulletins released–5.6.7/6.1.3</h1> <p>Thu, 02 Feb 2012 16:12:59 GMT</p> <p>The 5.6.7 and 6.1.3 CE and PE/EE versions of DotNetNuke have been released. The release notes can be read @ <a href="http://www.dotnetnuke.com/Resources/Blogs/EntryId/3274/DotNetNuke-6-1-3-5-6-7-Released.aspx">DotNetNuke 6.1.3/5.6.7 Released</a> .</p> <p>The 5.6.7 release only contains these one security fix (as per our Sunsetted releases policy which can be read <a href="http://security.dotnetnuke.com/">here</a> ), which is rated “critical”. </p> <p>The bulletin for 5.6.7 can be read here:</p> <ul> <li><a href="http://www.dotnetnuke.comhttp://www.dotnetnuke.com/News/Security-Policy/Security-bulletin-no.63.aspx">Non-approved users can access user and role functions</a> – fix for a “Critical” issue</li> </ul> <p> </p> <p>The 6.1.3 release contain two security fixes, one of which was in 5.x and one which was introduced in the 6.x branch.</p> <p>The bulletins for 6.1.3 can be read here:</p> <ul> <li><a href="http://www.dotnetnuke.comhttp://www.dotnetnuke.com/News/Security-Policy/Security-bulletin-no.63.aspx">Non-approved users can access user and role functions</a> – fix for a “Critical” issue</li> <li><a href="http://www.dotnetnuke.com/News/Security-Policy/Security-bulletin-no.64.aspx">Radeditor provider function could confirm the existence of a file</a> – fix for a “low” issue</li> </ul> <p> </p> <p>Please note, we had an additional report of another issue shortly after the 6.1.2 release, however that had already been resolved inadvertently by an unrelated bug fix. As such this issue was resolved with the 6.1.0 release (it involved code introduced in the 6.x branch and does not impact 5.x). Whilst no code was changed in the 6.1.3 release we have chosen to publish a bulletin anyway to make users aware of it and to allow us to acknowledge the security researchers who raised the issue.</p> <ul> <li><a href="http://www.dotnetnuke.com/News/Security-Policy/Security-bulletin-no.62.aspx">Potential XSS issue via modal popups</a></li> </ul> <p> </p> <p><strong>As both 5.6.7 and 6.1.3 contain a “Critical” fix we recommend you upgrade as soon as possible.</strong></p> <p>If you're new to upgrading I recommend you read the "detailed installation guide" found <a href="http://www.dotnetnuke.com/Resources/Documentation/DownloadableFiles/tabid/478/Default.aspx">here</a> , and the excellent blog entry from Erik <a href="http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1459/Default.aspx">here</a> . For users who are running 4.6.2 or above, I recommend you read this blog <a href="http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1843/Default.aspx">entry</a> which details how to use the upgrade package to easily merge any web.config changes. The wiki also has a guide on <a href="http://www.dotnetnuke.com/Resources/Wiki/tabid/1409/Page/Upgrading-DotNetNuke/Default.aspx">upgrading</a> and the video section has a number of free <a href="http://www.dotnetnuke.com/Resources/VideoLibrary/tabid/1607/Default.aspx">videos</a> on both installing and upgrading.</p> <p>You can read more details about these issues and our security policy <a href="http://www.dotnetnuke.com/About/WhatIsDotNetNuke/SecurityPolicy/tabid/940/Default.aspx">here</a></p> <p> </p> <h3>Acknowledgements</h3> <p>We would like to thank Brandon Haynes, Ben Zhong, Richard Lundeen of Microsoft and Microsoft Vulnerability Research (MSVR) and Mark Litchfield from NGSSecure for responsibly disclosing the issues to us and allowing us to ensure updated releases were available that resolved them.</p><br /><a href=http://www.dotnetnuke.com/Resources/Blogs/EntryId/3276/Security-bulletins-released-ndash-5-6-7-6-1-3.aspx>More ...</a><div class="category">Category: <a href=http://www.dotnetnuke.com/Resources/Blogs/CatID/10.aspx>Security</a></div> </article> <article> <h1>DNN Events 05.02.02 Released</h1> <p>ernstpeter.tamminga@dotnetnuke.com — Thu, 02 Feb 2012 09:09:40 GMT</p> For this point release, we focused on stabilising by fixing a small number of bugs that popped up, sometimes as a result of new versions of DNN.<div class="tags">Tags: Events</div><div class="category">Category: <a href=http://www.dotnetnuke.com/Resources/Blogs/CatID/9.aspx>Development</a></div> </article> <article> <h1>ASP.Net WebForms and MVC are Dead to Me</h1> <p>joe.brinkman@dotnetnuke.com — Thu, 02 Feb 2012 03:03:43 GMT</p> <p><a href="http://www.dotnetnuke.com/Portals/25/Blog/Files/3/3275/Windows-Live-Writer-Embracing_3BD6-rip_4.jpg"></a>After working with ASP.Net Webforms for the past decade, the time has come to move on. I have enjoyed using Webforms and I was pretty good at bending ASP.Net to my will. Having recently tried some newer web frameworks I find that I am more productive than ever before. Over the past couple of years I have dabbled with ASP.Net MVC, jQuery and even WebFormsMVP but none of them truly held my interest for long. I never felt like they really offered solutions to problems that I was worried about. Because of my involvement with <a href="http://www.dotnetnuke.com">DotNetNuke</a>, and the fact that it relies heavily on Webforms, I found that I couldn’t justify the use of some of these technologies. Things like WebFormsMVP added too much friction to the way I was used to working. ASP.Net MVC couldn’t really work in any meaningful way with DotNetNuke. And jQuery was a nice add-on, but it didn’t fundamentally change the way I developed modules.</p> <div class="tags">Tags: ASP.Net,Webforms,KnockoutJS,javascript</div><div class="category">Category: <a href=http://www.dotnetnuke.com/Resources/Blogs/CatID/9.aspx>Development</a></div> </article> <article> <h1>DotNetNuke 6.1.3/5.6.7 Released</h1> <p>israel.martinez@dnncorp.com — Tue, 31 Jan 2012 23:44:00 GMT</p> <p>I’m pleased to announce that DotNetNuke 6.1.3 and 5.6.7 are officially released. These maintenance releases contain several updates which further emphasizes our commitment to making the 6.X version of DotNetNuke the highest quality version ever. We will continue to release maintenance updates as needed while we continue to see more users upgrade to take advantage of the features included in 6.0 and 6.1. </p> </article> <article> <h1>Media Module Version 04.02.00 Released</h1> <p>will.strohl@gmail.com — Sun, 29 Jan 2012 10:43:04 GMT</p> <p></p> <p>The next version of the Media Module for DotNetNuke is once again here! In previous releases, ground-breaking features like oEmbed were added. In future releases, expect to see mobile rendering and HTML5 to be in the mix. Today, there were a handful of things that needed to be taken care of before taking this module to the next level.</p> </article> <article> <h1>Open Graph Protocol Module for DotNetNuke Version 01.01.01 Released</h1> <p>will.strohl@gmail.com — Sat, 28 Jan 2012 06:19:31 GMT</p> <p></p> <p>First, I would like to thank everyone for the feedback and support since the original release of this module. It’s been quite interesting. This module has many things planned for it, but I did want to make sure it lived in the wild for a bit to fix any issues that have been found before I begin adding more features. As it turns out, there were two significant fixes that were required.</p> <div class="category">Category: <a href=http://www.dotnetnuke.com/Resources/Blogs/CatID/9.aspx>Development</a></div> </article> <article> <h1>This is why DNN 6.2 is going to ROCK</h1> <p>israel.martinez@dnncorp.com — Mon, 23 Jan 2012 02:41:00 GMT</p> <p>A few weeks ago I was having dinner with some non-techy close friends (this group is made of medical doctors, cancer researchers and a photographer – definitely an interesting mix). The conversation was about the economy, the situation in Europe and at one point we started talking about social media / social networking. One of my friends said: “I really don’t get what the big deal is about social networking, I’ve been socially networking since I was little, actually, we’re socially networking right now”.</p> </article> <article> <h1>Let’s Build a Module #3–Output Formatting</h1> <p>steve.fabian@dotnetnuke.com — Mon, 16 Jan 2012 21:23:01 GMT</p> <p>The Gooddogs DotNetNuke Technology Template includes the Blueprint CSS Framework, and this blog post / video will show you how to use the framework to control the formatting of your module’s output.</p> </article> <article> <h1>Let's Build a Module #2 - Project Template Installation</h1> <p>steve.fabian@dotnetnuke.com — Tue, 10 Jan 2012 05:00:00 GMT</p> <p>The Gooddogs Technology Project Template for DotNetNuke module development is now available in an early form for you to download and try out. This Visual Studio 2010 project template is pre-configured to allow you to build DotNetNuke modules using the latest technologies like Entity Framework, WCF Data Serviced, popular open source frameworks like Knockout,js, AutoMapper and the Blueprint CSS Framework</p> </article> </main></body></html>