Joe Brinkman

OpenForce Call for Speakers Extended

joe.brinkman@dotnetnuke.com — Tue, 22 Apr 2008 01:25:00 GMT

The OpenForce Call for Speakers was scheduled to end today, however due to some issues with the original session submission forms we have decided to extend the call for speakers submission date. Please submit all session proposals by 5PM PST on Friday April 25th.

We have a lot of great sessions already submitted but we want to make sure that all speakers have an opportunity to get their session proposals submitted. If you are having any problems with the session submission, please send me an email and we'll take care of it promptly.

OpenForce North America Call for Speakers

joe.brinkman@dotnetnuke.com — Thu, 03 Apr 2008 19:01:00 GMT

DotNetNuke OpenForce is Back!

After a highly successful OpenForce '07 it is now time to begin planning for OpenForce '08. We are currently working with our conference partners on the OpenForce '08 conferences. One of our first tasks is to start identifying our speakers.

PowerShell for DotNetNuke

joe.brinkman@dotnetnuke.com — Mon, 15 Oct 2007 14:34:19 GMT

The following is an excerpt from my blog at TheAccidentalGeek.com:

With all of the excitement and passion in the PowerShell community, how could I not look to see how I could use PowerShell with DotNetNuke. Thus was born my session idea: PowerShell for DotNetNuke which I will be presenting in Las Vegas at OpenForce '07. During my session I will be showing how you can use PowerShell to enhance managing DotNetNuke, both for installing new sites and for sites that are already up and running.

One of the early ideas I had was that I might even be able to create a DotNetNuke module that would let a user execute PowerShell commands and scripts on the server. Since DotNetNuke allows you to lock down access to any module it is fairly secure. The initial code for this module is based off earlier examples by Scott Hanselman and Dominick Baier. Here is a sample video of my work so far.

See my full blog to download the source code.

DotNetNuke 4.6.2 is now available

joe.brinkman@dotnetnuke.com — Mon, 01 Oct 2007 11:31:23 GMT

Nothing is ever easy in life. The release of 4.6.0 and the subsequent release of 4.6.1 proved that. 4.6.1 was primarily concerned with fixing a couple of very nasty bugs from the 4.6.0 build. The two worst bugs included a breaking change to the behavior of ModuleSettingsBase and a defect in the UserSettings page that caused the system to overwrite your usersettings whenever someone logged in. Unfortunately, when we attempted to roll back the changes to ModuleSettingsBase to the pre-4.6.0 code, we did not get all of the relevant code rolled back. This only made the breaking change worse. This prompted us to take the unusual step of completely removing the 4.6.1 download until we could get a new version coded, tested and built to put back online.

OpenForce Europe is a Huge Success

joe.brinkman@dotnetnuke.com — Thu, 27 Sep 2007 01:22:55 GMT

Last week DotNetNuke OpenForce Europe '07 kicked off our first round of officially sponsored conferences for the DotNetNuke community. We have been planning for the OpenForce conferences for over a year and it was great just to get the first one out of the way. Since we have never put together a conference before, we were not always sure what to expect. The European conference was added in the early summer to our conference lineup, and we did not have as much time as we wanted to get all of the desired marketing pieces in place, but our European community members did not let us down.

DotNetNuke 4.6.0 release is coming

joe.brinkman@dotnetnuke.com — Wed, 12 Sep 2007 21:06:33 GMT

DotNetNuke 4.6.0 is quickly approaching the release date. We have gone through 2 different beta releases and have now packaged and released RC1 to our testers and benefactors.

DotNetNuke 4.6 Roadmap

joe.brinkman@dotnetnuke.com — Sat, 04 Aug 2007 21:27:21 GMT

With DotNetNuke 4.5.4 and 4.5.5 having recently been released, we are now well underway on the 4.6 release. Unlike previous releases we actually started work on some elements of this release in parallel with 4.5.4 release testing. What has not been decided until earlier this week was the full scope of the release and a target release date. The exact feature set and release date is still subject to change.

Refining the DotNetNuke Release Process

joe.brinkman@dotnetnuke.com — Tue, 24 Jul 2007 15:46:32 GMT

Over the last four years DotNetNuke has experienced tremendous growth and adoption. We have added more features to the core and grown the project teams to the point where there are now more than 45 people actively working on one DNN project or another. At the same time we have also grown the programs around the project that help fund DotNetNuke and provide support to the community - programs like the Benefactor Program, the Review Program, the MarketPlace and the upcoming OpenForce Conferences.

Re-defining Open Source

joe.brinkman@dotnetnuke.com — Tue, 10 Jul 2007 21:18:03 GMT

The following is re-published from my blog at TheAccidentalGeek.com

It seems that I am seeing more and more discussion around what constitutes Open Source software and Open Source projects. Not only do you have the Free Software group who follow the Richard Stallman philosophy and the Open Source group who fall more into the Eric Raymond camp...

PowerShell and DotNetNuke

joe.brinkman@dotnetnuke.com — Sat, 07 Jul 2007 22:00:10 GMT

Having worked with DotNetNuke for more than 4 years now, I have performed literally hundreds of installations. While the installation process has gotten easier over the years as we have beefed up the installation routines, it is still not automatic. Even though I can install DNN in under a couple minutes, I often cut corners. I usually just give the Asp.Net process account full control of the web application folder and use an sa account in the DB. Neither of these are great practices, but setting up the correct permissions is a little more tedious and after you perform this task dozens of times you find that you soon start taking shortcuts. The downside to these shortcuts is that I am not really testing out my site in a configuration that mirrors a typical production environment. This can lead to subtle bugs that will be harder to track down later.

The full blog post is availble at my new blog.