Earlier this year, the Q&A; module was released to the community as a beta and installed and serves as the Community Exchange on dotnetnuke.com. As awareness of the Community Exchange increased, I started getting more and more questions about the module and how user's can have more insight into how they gained reputation. At the time, I didn't really have anything to make this possible. It was also about this same time that I started to get some idea of the new opportunities the DotNetNuke 6.2 release was going to provide developers. The result of this is a few updates to the module that gives users what they are asking for while leveraging some of the most exciting new features in the DotNetNuke 6.2 release (which were only possible due to the efforts of our engineering and QA teams who did an excellent job with this release).
If you haven’t learned yet, the Day of DotNetNuke always has surprises that are only available to people that actually go to the event. It’s always been my style to save the best for last in terms of announcing those surprises. Also in that bucket is that I want for those that physically attend DotNetNuke events get the very best in value when these plans are made. If this hasn’t taught you anything, it should teach you this… DO NOT miss the Day of DotNetNuke. This year, the surprise is not just one, but TWO surprises. These surprises have been kept so quiet that the local event organizers and even people at DotNetNuke Corporation didn’t know.
This year DayOfDNN is hosted in Charlotte, NC on June 2. Although the timing of the event isn't perfect for me since I've been on an extended vacation and now trying to catch up with things. But I've never been to Charlotte before so I'm looking forward to visiting.
I'm speaking this year on the responsive design topic. For those of you who aren't familiar with it, it is a technique to create websites and web apps targeting various devices based on their resolution.
I look forward to meeting with old friends and making ones at this event. It'll be a great one! Just in case you're going, below is the description of my talk. See if you can make it and I'd love to chat more about it if you are interested in learning how.
In case you missed it, DotNetNuke 6.2 was released today, check out Will Morgenweck’s blog post for more details on the release.
With some of the new features DotNetNuke 6.2 makes it easier to start to customize the listing of members on your site, and also the Profile display for users on the website. I started implementing DotNetNuke 6.2 on one of my racing websites last night (yeah, so I upgraded before the release happened, a benefit of working for the corp).
In doing so I configured the profile pages on the website to use some of the new 6.2 functionality, before I show you the code, here’s a link to my profile over there, so you can see what all I implemented. This is far from complete, plenty of more work to be done, but it provides far more information than the profiles did two days ago.
I am pleased to announce the release of DotNetNuke 6.2! This release marks a significant milestone as we continue to redefine CMS as Cloud, Mobile and Social. Keep reading to learn about all the new features in DotNetNuke 6.2 that will help you quickly build applications to improve collaboration, communication and employee productivity.
Just a quick note that will hopefully save a few of you early adopters some frustration. Between the initial unveiling of Services Framework back in March in CTP2, and the upcoming RTM there have been several tweaks made to the public API. The two biggest changes both affect route mapping.
IServiceRouteMapper.RegisterRoutes now takes an IMapRoute parameter. Simply change the type in your method declaration from ServicesRoutingManager to IMapRoute.
The next change is sneaky and has already tripped up several people at DNN Corp.. The name parameter has been removed from the MapRoute methods and all it’s overloads. In early versions name was the second parameter of all the MapRoute overloads. Because the various overloads all take a combination of string and object types, odds are your old code will compile without error. However your routes will no longer work because, for example, your old name parameter is now getting used as the url parameter. Generally deleting the name parameter from any calls to MapRoute will fix this problem.
I’m quite excited to see Services Framework is already getting some real traction in the community, and it’s not even officially released yet. If you are excited about Services Framework, it would be a good idea to make your way to Day of DotNetNuke in Charlotte on June 2, 2012. Both Brian Dukes and myself will be giving presentations with a major focus on Services Framework. And I know a few other presentations will include Services Framework to a lesser extent as well. Additionally many people who already have experience using Services Framework in production code as part of 6.2 and other DotNetNuke Corp. projects will be there including Joe Brinkman, Will Morgenweck, Charles Nurse, and Ian Robinson. There has never been so much Service Framework experience in one place before, I look forward to seeing you there.
I am happy to announce that we will webcast the DNN 6.2 launch event which will take place at our worldwide partner advisory council meeting in Sonoma, California on May 30, 2012 at 9am PDT. During the broadcast, DotNetNuke Corp. CTO and Co-Founder, Shaun Walker will present the DotNetNuke vision and roadmap for merging social collaboration with web content management. Shaun will be joined by Will Morgenweck, DotNetNuke Corp, Director of Product Management. Morgenweck will demonstrate how the new social collaboration features can be used to deploy online social communities that help turn prospects into customer and customers into brand advocates.
KnockoutJS is taking the ASP.Net world by storm. DotNetNuke 6.2 will include several core features which rely heavily on KnockoutJS. In Part 1 and Part 2 of my Introduction to KnockoutJS series I discussed some of the basics of bindings which are at the heart of KnockoutJS. Later this week, I’ll continue my series on KnockoutJS. In the meantime I wanted to highlight a great learning opportunity for those who are interested in learning how to use KnockoutJS with DotNetNuke. Given its usage in DotNetNuke 6.2 it should come as no surprise that KnockoutJS will be prominently featured at the Charlotte Day of DotNetNuke on June 2nd.
After nearly 7 months, the finish line is finally in sight. With the final touches applied to the product over the past few weeks, we are confident that we are on track for an exciting new product release.
As a bit of a refresher on the release terminology that we use in the DotNetNuke community, I would encourage you to read the blog written by Joe Brinkman last year titled "What's In A Name?". The blog explains that by the time we hit a Release Candidate, the product is pretty much frozen. We have gone through all the major test scenarios and are just running through a final set of regression tests and verifying the packaging. In the absence of any major show-stopping bugs, this is the product which will be released. At this point we only have a week or two until the anticipated release date and are really just taking one last look before we release the product. Any issue found at this stage will likely just be logged in Gemini and be scheduled for correction in a follow on maintenance release.
Almost exactly one year ago I posted a blog which highlighted the three most pervasive technological trends in the software industry and predicted that the Content Management market was in for a significant disruption in the coming years as it attempts to get comfortable with these new technologies. This same blog was republished with Bryan Ruby’s permission on the CMS Report website.
This morning I kicked off Day 2 at CMS Expo in Chicago, IL with a mini-keynote on this same topic. But rather than just talking about what cloud, mobile, and social represent from a technology perspective, I also tried to explain WHY these trends have come to the forefront in recent years.
At a fundamental level I believe they are actually driven by globalization. And globalization would not have been possible without some critical infrastructure, specifically Internet connectivity, access to broadband, and affordable mobile devices. These innovations provided the basis for a global distributed workforce. However, they alone were not enough to generate the expected return on investment in terms of increased business efficiency and productivity. Rather, this required the emergence of collaborative business networks – networks which could provide the necessary collaboration, coordination, and communication to forge deeper business relationships and more meaningful interactions. And these collaborative business networks rely on those three industry trends which we are all very familiar with now: cloud, mobile, social – also known as systems of engagement. Systems of engagement are critical for getting the most out of a global economy.
In the context of Content Management, we firmly believe that your CMS will continue to be the central hub of your business. However, we also believe that in order to adapt to the changing landscape, your CMS will need to be fully and deeply integrated with systems of engagement. The resulting solution is a perfect marriage of content creation and content delivery. And in looking at the innovation adoption lifecycle, we believe that the cloud, mobile, and social trends have already jumped the chasm and are well on their way to gaining mainstream adoption in the mid-market.
In summary, we believe the future of C.M.S. is already being redefined as Cloud, Mobile, and Social. And we are taking steps to ensure DotNetNuke is ready for this transformation.
The slides for my mini-keynote can be dowloaded here.
The release of the DotNetNuke 6.2 Beta 2 was really the first chance users had some insight into what their installs might look like after upgrading to 6.2. In the previous beta of the blog module, the majority of the changes were on the administration side of the module or behind the scenes. In this beta release, the majority of changes are around things content authors and blog readers typically see. So similar to the core beta 2, this module beta 2 will offer blog module users some insight into what they should expect to see in the final release. Also similar to the core beta 2 is that this is the last chance to test and submit your issues to the project's issue tracker.
Over the last many months the Engineering Organization at DotNetNuke Corp. has been making many process changes to deliver high-quality Software. As Scrum Master and Lead Developer, I’d like to dedicate a blog series on what we did, how it helped and the lessons we learned.
In this blog, I’d like to talk specifically about Peer Code Review that we implemented over 10 months ago.
This year’s DotNetNuke World conference is just around the corner and we are once again looking for speakers. DotNetNuke World will be October 10th through the 12th in lovely Orlando, Florida. Registration will be opening soon, and like last year we will be offering great early bird pricing. This year’s event is shaping up to be twice as large as last year. More speakers, more sessions, and more attendees.
Much like past years, we are accepting session submissions that focus on Development, Design, Administration and Business. We have expanded the number of rooms this year so that we could accommodate more sessions with a broader appeal to business decision makers and end users. This year’s conference will focus on the “Social Revolution” but other topics are equally welcome.
On Friday, May 4th I am excited to travel to sunny Florida and present to the Sarasota .NET Developers Group ( SarasotaDev ). The presentation will take place at the Sarasota Community Foundation located at 2635 Fruitville Rd in the afternoon from 2:00-4:00 PM. I plan on covering a couple of topics related to DotNetNuke which I think the audience will find highly engaging. The first topic being a presentation and demo of the highly anticipated DotNetNuke 6.2 release which fully integrates the ActiveSocial functionality and transforms the application into a powerful Social CMS. And the second topic being an exploration of technology trends as they relate to Microsoft developers and how DotNetNuke intends to adapt to these trends to ensure it remains a highly relevant web platform for the future. I want to shout out a special thank you to Stan Schultes for arranging the venue and logistics for this event. Following the presentation, the group is invited to attend a great party with awesome pizza, appetizers and drink tickets at the Broadway Bar where we will help kick off the BarCamp Sarasota weekend starting at 5:30pm.
On Saturday, May 5th I am excited to participate in my very first BarCamp conference. The BarCamp Sarasota Spring Conference 2012 is taking place on the weekend of May 5th & 6th at G.WIZ – The Science Museum at 1001 Blvd of the Arts in Sarasota. The 2 day event is full of interesting speakers and sessions, great roundtables and workshops, open-space conversations, and killer parties. I plan to present two topics on Saturday: “C.M.S. Redefined: Cloud. Mobile Social”, a session which highlights the three most disruptive technology trends in recent years and how they will influence the future of Content Management; and “The Business of Open”, a journey through the history of the DotNetNuke project as it evolved from an organic open source project to a venture-backed commercial enterprise.
One of the new features in DotNetNuke 6.2 is the Member Directory. During the implementation of this new feature, we ran into some stumbling blocks trying to retrieve user info and user profile information. The issue wasn’t retrieving the necessary information, it was the speed at which the queries were performing at.
The last beta for DotNetNuke 6.2 is now available. That’s correct, this is the last beta. That means we are feeling really good about where we are with the product. The team is working hard to stabilize the release, but we still need your feedback! We still have some issues to work through, but we are getting close to the public release of DotNetNuke 6.2. Learn more about how to get started with DotNetNuke 6.2 today!