The Mighty Blog

Upcoming .Net Community Events in Florida

wills@strohlsitedesign.com — Thu, 02 Jul 2009 15:10:00 GMT

There are quite a few events coming up in Florida in the next few months. They are all free, and most will give you the opportunity to win free stuff just for showing up. Awesome! If you find yourself in or around any of these events, I strongly recommend you stop by. I have been to most of them, and they are great.

All of the following information came from the Orlando DotNetNuke® Users Group (ODUG) website. See our events page.

July 9 - Orlando DotNetNuke® Users Group
Will Strohl (nobody) will be talking about the Core DNN Blog Module.

July 14 – Orlando PASS
Chad Miller will be discussing Powershell with SQL Server.

July 15 – Space Coast .Net User Group
Oleg Sych will be presenting on VSTS and TFS.

July 16 – Orlando .Net User Group
Joe Healy (Microsoft Developer Evangelist) will be speaking about the developer features in IE8.

July 16 – Space Coast SQL User Group
Don King and Clay Seifert will be each presenting a different session. They will be speaking about SQL Server 2005 Clustering and SQL Server Analysis Services, respectively.

July 21 – Lakeland .Net User Group
This user group will be holding a session entitled “Lakeland’s .Net Speaker Idol” and it promises to be a fun time, where you will see speakers compete against each other for prizes.

August 4 – Orlando DotNetNuke® Users Group
DNN author, Darren Neese will be showing the new features in the DNN skinning engine.

August 18 – Space Coast .Net User Group
Topic and speaker TBA. (sorry…)

August 20 – Orlando .Net User Group
Christopher Bennage (MVP) will be showing the attendees SilverArcade.

August 20 – Space Coast SQL User Group
Joe Healy (Microsoft Developer Evangelist) shows the group SQL Server 2008 enhancements from a developers perspective.

August 29 – Jacksonville Code Camp
The Jax Code Camp crew overcame some very challenging obstacles last year. I was extremely impressed. I expect them to put on a great event again this year.

September 5 – Tallahassee Code Camp
Tallahassee Code Camp was a great time last year. They always have some great presenters on-hand.

September 10 – Space Coast SQL User Group
Jack Corbett will be presenting a yet to be determined topic.

November 5 – Orlando DotNetNuke® Users Group
DNN Blog Project Team Lead, Antonio Chagoury, will be presenting “Mashing Up Your DotNetNuke Using RESTful APIs.”

Technorati Tags: DotNetNuke,DNN,DNN Blogs,.Net,Code Camp,Events,User Group,ODUG,Orlando DotNetNuke Users Group,ONETUG,Orlando .Net User Group,Space Coast SQL User Group,Space Coast .Net User Group

How to Manually Delete A DotNetNuke Module

wills@strohlsitedesign.com — Sun, 28 Jun 2009 22:31:00 GMT

I was recently asked how someone could manually delete a module once it is installed. The number of use cases where this would be useful is limited, but it is still a valid scenario that needs to be considered – especially during development. Here is a walk through of the general steps required to delete a module manually.

Run the Uninstall script (if necessary)
Delete the module files from the DesktopModules and App_Code folder
Grab the DesktopModuleId
Delete the permissions associated with the module
Delete the module from the database
Refresh the site cache to update the UI with your changes

While I have not fully verified these steps to be the same in DNN version 5.x, they should generally be the same. Here is some guidance to follow each of the defined steps above…

WARNING! Performing these steps incorrectly could result in your DNN site being broken and/or no longer accessible. In some cases, this might be permanent. It is HIGHLY recommended that you perform a complete backup of your database and file system before performing these steps. Doing so will give you a restore point, should something go wrong.

Run the Uninstall Script

Not all modules require a Data Access Layer (DAL), as some modules only perform utility functions and do not need to save and retrieve information from the database. The majority of the module out there do have a DAL though, and in turn will have an uninstall script in their folder. Look for a file named Uninstall.SqlDataProvider in the DesktopModules folder for the module you’re deleting. Here is a reference path for you to use:

~/DesktopModules//Uninstall.SqlDataProvider

Assuming your module is named “WNSUtility”, the above path would look like this:

~/DesktopModules/WNSUtility/Uninstall.SqlDataProvider

Using the SQL Module in the Host Menu, execute this script. Be sure to load the script, and then check the checkbox for Run as Script before you execute it.

Please Note: If you are using a different Data Provider, the file extension for your uninstall script will be different.

Delete the Module Files

Deleting the files from a module is easy. Find the module directory for your module. Using the example from above, it would be:

~/DesktopModules/WNSUtility/

Delete all files from that directory, and the directory itself. You might run into one or more errors do to files being loaded into memory. Should this happen, you can release the file(s) from memory by recycling the Application Pool, or restarting IIS.

Grab the DesktopModuleId

This is a very important step, as the final two steps would be incredibly difficult without the DesktopModuleId. There is not always an exact science to finding the DesktopModuleId, but we will need it for the following steps. In most cases, I simply perform the following query on the database:

     SELECT * FROM [dbo].[DesktopModules] 

    WHERE [IsAdmin] = 0 

    ORDER BY [FriendlyName] 

    -- or 

    SELECT * FROM {databaseOwner}{objectQualifier}DesktopModules 

    WHERE [IsAdmin] = 0 

    ORDER BY [FriendlyName]

From the above script, locating the module in question is usually easy. Simply find the module using its Friendly Name, and then record the DesktopModuleID associated with it.

Delete the Module Permissions

This step gets executed in three parts. As long as there aren’t a lot of instances of the module in your site, these queries should execute quickly, and error free.

Using the DesktopModuleId from the previous step, execute the GetModuleDefinitions stored procedure, taking note of each ModuleDefID. For each module definition returned, you will next need to execute the GetPermissionsByModuleDefID stored procedure, this time taking note of each PermissionID. Finally, execute the DeletePermission stored procedure for each PermissionID that was returned.

Delete the Module from the Database

Now, we actually delete the module. Doing so is very easy. Like the previous step, we just need to execute a stored procedure using the DesktopModuleID we grabbed a little while ago. Execute the DeleteDesktopModule stored procedure to delete the module.

Refresh the Site Cache

The final thing to do is to clear the cache on the site to remove the module from all of the user interface, such as the drop down lists. You just need to clear the cache on the site. I have blogged about clearing the DNN site cache before.

Technorati Tags: DotNetNuke,DNN,DNN Blogs,Module Development

Changing the Default Favicon for Your Site

wills@strohlsitedesign.com — Sun, 28 Jun 2009 04:33:00 GMT

In DotNetNuke®, a favicon of the DNN gear logo is placed as the default favicon. For some websites, this is no big deal. However, for any site that requires its own branding, changing the favicon is a really big requirement. Luckily, DNN makes changing this easy, and flexible.

First of all, in the root of your DNN site, there are two favicons:

favicon.ico
DotNetNuke.ico

Both files contain the same image, the DNN gear.

You could just overwrite the favicon file with your own. However, that is technically making a core code change, and if you end up putting a second portal on your DNN instance, both sites will be using the same favicon. This will likely put you into the same position that you originally were in, in the first place.

The real solution is to put your favicon into the root of your portal directory, saved as favicon.ico. For example, for the root site, your file name and path might match the following:

~/Portals/0/favicon.ico

When your site is loaded, the DNN framework will automatically grab and send the new favicon to the web browser, instead of the one on the root of your DNN installation. This will work for each and every portal that you have as part of this single DNN instance. For example, if you have 50 portals hosted in your DNN instance, each one can have its own unique favicon using this method.

Technorati Tags: DotNetNuke,DNN,DNN Blogs,Favicon

ODUG Celebrates it’s One Year INETA Anniversary

wills@strohlsitedesign.com — Sun, 28 Jun 2009 00:06:00 GMT

The Orlando DotNetNuke® Users Group (ODUG) is not very old. We are still working toward finishing our second year as a user group. Our first meeting was February of 2008. However, it was several months later before we actually were able to claim our status as member of INETA. Well, a few days ago I was reminded of this, as there was a package that showed up for me at work.

Looking at the package, I was confused since it was from INETA. I wasn’t expecting any packages, much less one from INETA. When I opened it, I was greeted with a pleasant surprise. It was a mounted certificate, celebrating our one year anniversary with the INETA user group program.

For those of you who are not sure what that means… INETA sponsors user groups in a way that most other organizations cannot. It gives support in a number of ways to user group leaders. The most notable way they sponsor user groups comes in the form of flying in speakers. INETA provides two speakers per year, with all of their expenses paid. So far, we have only used one of these. INETA flew in Chris Hammond to us earlier this year. We are already planning to use our 2nd one in December of this year.

I have only one thing to say, “Thank you, INETA!”

Technorati Tags: DotNetNuke,DNN Blogs,INETA,User Group,ODUG,Orlando DotNetNuke Users Group

Comparing the DotNetNuke Podcasts

wills@strohlsitedesign.com — Sat, 27 Jun 2009 01:03:00 GMT

I wasn’t really listening to podcasts until a few months ago. I just really didn’t find anything that truly interested me to the point of putting down my personal 60+ GB of music and streaming my favorite radio stations. Not to mention, I am a fan of the popular streaming service known as Pandora. Anyway, I found the DotNetNuke Podcast about that time, and shortly after, DNN Voice was born. Since I am so passionate about DotNetNuke®, I began listening. Right now, I only know of those two DNN podcasts.

I have been listening to both podcasts for a while now. Honestly, I like them both. They have a different focus, and because of that focus, both are going to have a different fan base.

DotNetNuke Podcast

Address: http://www.dotnetnukepodcast.com
Host(s): Lee Sykes and Richard Wooten (cannot find personal blog links)
Background: Lee Sykes is the original person behind the DNN Creative Magazine website, which sells DNN tutorials and videos. It has become one of the primary places to get DNN “how to” information on the Internet. Richard Wooten is also part of DNN Creative, since February of 2008. Both have been using DNN for a long time, and have a great deal of knowledge in using DNN.

It is fun to listen to the DotNetNuke Podcast. Lee and Richard have a great chemistry, and it translates well into the podcast. They basically speak about of the new things that they have heard about in the DNN ecosystem. It almost feels like they each have a separate list of bullet points. They talk about community news and information, but it usually not very much of their podcast. Overall, they have some great information.

I love their summary on their website for each episode. While it doesn’t look like their is a whole lot of organization to the information, it is well laid out for us to follow along on their site. There is an RSS feed that is available to you to help you keep track of new episodes. I have also seen Lee promote the shows on twitter. Since I check twitter more often than I do my RSS reader, that’s how I usually get informed of the newest episodes.

In their About Us page, they ask for community input for the show. That is really cool. I haven’t noticed them mention any of their content coming from this feature though.

Some of their ecosystem “news” is sponsored. While I understand why, and I don’t disagree with it (I am beginning something similar on my blog), I would much rather hear about ecosystem products and news that they find interesting or are passionate about for personal reasons. In the end, it is still good information though, so it isn’t a deal breaker at all for me.

I am disappointed that community information doesn’t take a higher priority in the information they pass on to their listeners. In my opinion, the community information is often more important than the ecosystem information. Sure, they mention something about community here and there, but it is clearly not as much of a priority as I think it should be.

Something I really do not enjoy is the other tech news that get injected into the podcast, and this is a deal breaker. The podcast is called “DotNetNuke Podcast”. When I listen to it, I do not expect or want to hear about other technologies unless they have a relationship to the word “DotNetNuke”.

DNN Voice

Address: http://www.dnnvoice.com
Host(s): Chris Hammond and Tom Kraak
Background: Chris Hammond is a DNN Core Team Member, and the Project Lead for the Wiki Module. In addition, he is the for Engage Software, the Official DotNetNuke® training provider. Tom Kraak is an SEO Expert and principle consultant at Seablick Consulting, specializing in the DNN ecosystem. Like Richard and Lee, Chris and Tom have been using DNN for quite a while and have a great deal of DNN knowledge.

Full Disclosure: Even though I feel that I am pretty good at being objective, I do feel that it’s only fair to let you know that I have developed a personal relationship with Tom and Chris. We speak regularly on twitter and the IM, and I have had them speak at our ODUG meetings. Also, I did give some input to Chris about the podcast for the first few episodes. So, while I believe that my review here is completely objective, you can use your own judgment and form your own opinion when I am done.

The DNN Voice podcast is very well-structured. I has a pre-defined format that it follows the same path for nearly every episode. For those of us that are techies (most of the audience), it gives us the routine that we typically enjoy. I really like that the various sections have an audible queue to let us know when the next section is coming, and what it is. Like the radio, it helps us to know when the next segment is coming.

Similar to Richard and Lee, Chris and Tom also have a great chemistry and it comes across well during the podcast. Both podcasts do a great job of keeping each episode fun in the same way. It sounds like we are eavesdropping on two friends having a good time talking about technology.

DNN Voice places a much higher emphasis on listener input by making it a prominent link on all pages on the site. They also make this part of each episode, making it clear to the listener that their input is not only welcome, but they might hear it on the show.

In general, I do not think that we could have a podcast that isn’t sponsored in some way. We must find a way to justify the time we spend on projects such as this. DNN Voice’s sponsorship is less transparent than the previous podcast. It is clear that the podcast has an affiliation with Engage. Once again, this is not a deal breaker.

The main thing I really love about DNN Voice is that it appears to be a much better mix of community and ecosystem information. This is very important to me. In my opinion, the ecosystem is only successful and exists because of the community.

Like the DotNetNuke Podcast, DNN Voice makes its announcements for the podcast available through RSS and twitter. However, DNN Voice takes this a step further by making the show available as a subscription through Zune and iTunes. Also, while both podcasts offer up a comments mechanism on their site, DNN Voice takes this another step further by allowing their visitors to rate each individual podcast.

In Conclusion

Each podcast definitely has its own focus and specialty. DotNetNuke Podcast seems to cater to the DNN’er who is mostly concerned about technology in general, and the DNN ecosystem. DNN Voice appears to have its focus pointing directly at the DNN community member, and still includes more information, but stays within the DNN umbrella.

I think it’s clear that I prefer DNN Voice over the DotNetNuke Podcast. However, I cannot say that one is better than the other. That depends on what you want in a podcast. They each fill a void in the DNN podcast market. However, all of the voids are not yet filled… Any new podcasters out there? :)

Technorati Tags: DotNetNuke,DNN,DNN Blogs,Podcast,Review

Review: Lenny’s Sub Shop in Tampa, FL

wills@strohlsitedesign.com — Sat, 27 Jun 2009 00:09:00 GMT

Today, part of the family and I had to go to Tampa, Florida for an appointment. Of course, when the appointment was over, it was after lunchtime. We proceeded to look for a place to eat near us. We ended up finding what looked like another small business sub shop from the outside. I soon found out I was wrong, but it was still a great visit!

What I thought was a small-time sub shop turned out to be a nationwide chain of franchise stores. There are 13 so far in the state of Florida, with one in Orlando, and 3 in Tampa. Something confuses me about my post-visit research of this place though. Their door says, “Delicious Subs & Philly Cheesesteaks Since 1979.” Yet, their own website says that the first location opened their doors in 1998, in Memphis, Tenneessee. That’s quite a discrepancy in dates, and a poor display of branding. For a restaurant that appears to put a lot of effort in branding (see pictures below), I was pretty disappointed.

They have branded everything in the store, from the chips to hot pepper relish, and signs to napkins and everything in between.

The location in Tampa that we visited was in North Tampa on Fowler Avenue, which is actually known as Temple Terrace. They’re even part of the local Chamber of Commerce.

The service was really outstanding. For those of you that follow my blog, you know that of all things in the world, I am most critical of customer service. The two gentlemen working up front really did a great job of taking care of us, and making sure that everything we wanted was taken care of. It was definitely a challenging visit for them too. Kim had a really bad headache, the Coke tasted like the syrup was low, and the women’s toilet was out of order. We reported the the latter 2 things to them, and they were extremely accommodating of our requests.

The prices appeared to be average of what we’d expect to pay in any other sub shop in Tampa, or Orlando. However, the upcharge for making a sandwich a meal (a choice of chips or a cookie, and a medium soda) is a whopping $2.09 for a regular sized meal. However, large sandwiches have additional $0.30 for the upcharge, and it’s not clear why. My drink was the same size as everyone else’s.

They serve Coke products, and accept the major credit cards. This is always a plus for me, as I rarely carry cash. They also do not use preprocessed meats in the sense that they cut all of their meats onsite.

There were only 3 of us there today: Kim, Paige, and I. Here is what we ordered…

Kim ordered the Chicken Salad sandwich. It was #17 on the order board, and came with the typical options for their sandwiches. She chose wheat bread, and no other toppings, just plain. I tried her sandwich, and she made a great choice. The chicken salad is delicious all on its own. I found it to be full of flavor, moist, and the chicken was definitely white meat and fresh. The wheat bread was soft all over, and not even the least bit chewy – perfect!

Paige ordered the Kids Hot Dog (#25). She had a choice of having ketchup and mustard on it, and a wheat or white bun (not a hot dog bun). There are other toppings that I am sure she could have chosen too. Like the other meals, she had a choice of chips or a cookie. She chose Salt & Vinegar Chips. They were incredible! I wonder if they have their own brand, or if they rebrand someone else’s chips. I didn’t try her hot dog though, and I am not sure what brand of hot dogs they use.

Finally, it comes to me. I find that the defining moment for any sub shop on my first visit to any sub shop is how they make their Philly Cheesesteak. If I like it, I will return and I will like the restaurant. Otherwise, they permanently lost my business. If your Philly Cheesesteak sucks, please take the word “sub” out of your business name.

I do feel that I need to qualify my statement and my upcoming review of the sub. I am not one of those people that says that a Philly Cheesesteak needs to have any specific ingredients, or be cooked any specific way. I find such a thought to be close minded. Imagine if we felt the same way about pizza. We’d only have a cheese pizza. Food would be so boring if people did not put their own personal touches on a meal or dish. And just think about how few options we’d have in our daily restaurant selection. I believe that a Philly Cheesesteak begins with steak, cheese, peppers, and onions on a sub roll. From there, it’s whatever you decide.

I ordered the Philly Cheesesteak. Like the other subs, I had the choice of regular or large. I thought this meant 6-inch or foot long. I was very wrong. Apparently, this meant 1 sub or two. Hehehe… Among my other choices, I selected: wheat bread, lettuce, mayo, tomato, cheese, peppers, and their popular hot pepper relish. The relish was incredible! I have had similar relishes before, and they are so good! Just spicy enough to enjoy the flavor, with a touch of sweet to spike that extra bit entertainment into your palate. I also had their Jalapeno Chips, which tasted really good as well.

As you can see from the above picture, the large sub looks like two regulars.

I can sum up their philly in one word: DELICIOUS! The meat was tender and tasty. It tasted like it was definitely marinated, and kept moist before serving. The lettuce was typical lettuce and the same with the tomatoes – nothing special about them unfortunately. Everything about the sub appeared to be above average. The peppers and onions were just as delicious as the meat, and the hot pepper relish was a perfect compliment for the rest of the ingredients. It made my mouth do the happy dance!

In Conclusion

Overall, our visit to Lenny’s Sub Shop was a really great visit. It was a lucky find, for sure. We enjoyed the service, and the food was delicious. They really seem to have their own flavor, for a chain. Typically, you find a homogenized menu and meals at chains. Despite a broken toilet, the place looked clean. The prices do not make you run out the door. I would say that my only piece of constructive criticism would be to buy fresher produce, perhaps from local growers.

Give them a try! I am sure that you will enjoy your visit like we did.

Here are some final pictures of the location we visited:

Technorati Tags: Review,Restaurant,Lenny's Sub Shop,Philly Cheesesteak,Franchise,Tampa,Florida

How to Add a User to a Role Programmatically

wills@strohlsitedesign.com — Fri, 26 Jun 2009 00:07:00 GMT

There may come a time when you will want to programmatically add a user to an existing role in DotNetNuke®. It’s actually quite easy. If you take a look at how the core code in DNN does it, just emulate that. This method of using and reusing the existing DNN core code is what DNN development is supposed to be about, so make sure you don’t reinvent the wheel.

In the source code for DotNetNuke®, there is a controller class for nearly everything that you want to do with the various objects that you work with in DNN every day. Since I am familiar with the DNN source, I knew where to go. But many people are not familiar with the source code. In those cases, you need to either do some searches in the Object Browser, or browse around until you find the code you’re looking for. Thinking it through logically, you can usually browse right to the code you’re looking for since the core team has done a fantastic job of keeping the code files organized.

Keep all of that in mind, I immediately gravitated to the Security folder of the Components directory. I did this because roles are part of the security framework in DNN, and all of the entities and objects are in the Components folder. Inside this folder, I saw and opened the RolesController.vb file. To make this clear, I opened the following file in the DNN source code:

~/Library/Components/Security/Roles/RoleController.vb

The controller classes are usually what we are looking for when we want to utilize the existing logic in DNN. So, if I want to manage a role by putting someone into it, I naturally wanted to look for a Role Controller already – before I even opened the source code solution.

One of the methods of the RoleController class is AddUserRole(), and it has a few overloads. We are only concerned about the root method right now. This method accepts a few arguments, and when successfully called, it adds an existing user to an existing role.

     RoleController.AddUserRole(integer PortalID, integer UserId, _ 

        integer RoleId, date EffectiveDate, date ExpiryDate)

Using this method may look self-explanatory, but I will explain it anyway. When you intend to use this method, you should already have access to an existing UserInfo object, and a RoleInfo object. Both are regularly available through standard module development.

PortalID (integer) – This is the id number representing the portal where the user and role exist. The SqlDataProvider will use this value to correctly match up the objects.
UserId (integer) – This is the id number matching the user that you want to add to a role. Most often, you would simply access this value from the PortalModuleBase class that your module inherits.
RoleId (integer) – The id number of the role can be found from any number of ways. We can only assume that you already have access to this right now.
EffectiveDate (date) – This is the date that you want the role assignment to begin. Usually, the current date is what you’re intending to pass to this argument. This argument accepts a null value.
ExpiryDate (date) – This should be the date that you want the role assignment to expire, and as a result, the user will be removed from it. This argument accepts a null value.

In more recent versions of DNN, there is also another value which we do not pass to the method.

CreatedByUserID (integer) – This is a value implemented for auditing purposes, to let us know who added the person to the role.

Let’s assume that we have a UserID of 123 and a RoleID of 10. Going further, we will also assume that this is a first instance of a portal, equaling a PortalID of 0. The most common role assignments do not pass an EffectiveDate or an ExpiryDate. We will use this as an example as well. Here is how we would call the method:

    ' we are assuming that you already have an intRoleId from your logic

    RoleController.AddUserRole(Me.PortalID, Me.UserId, intRoleId)

    ' ... or ...

    ' Here we assume a role assignment for 30 days, beginning now

    RoleController.AddUserRole(Me.PortalID, Me.UserId, intRoleId, DateTime.Now, DateTime.Now.AddDays(30))

That’s all there is to it! :) Easy, right?

Technorati Tags: DotNetNuke,DNN,DNN Blogs,Membership,Code,Core,API

Web Browser Market Share from My Perspective

wills@strohlsitedesign.com — Thu, 25 Jun 2009 22:58:00 GMT

The trend recently seems to be that comments and topics are brought up on twitter, and they end up growing to be something more outside of it – especially in the world of DotNetNuke® that I have immersed myself in. Today was no different. A fellow DNN twibe member and also a member of the Orlando DotNetNuke® Users Group (ODUG), Mike van der Meulen, gave me a friendly jab about using FireFox. He said:

God! Why do you people all use FF, the rest of the world doesn’t :-)
That provoked a thought in me, “what is the current market share for the web browsers?” Not being a scientific study, I proceed to check 3 sources: my blog, W3Schools, and RezHub. They each have a different demographic. W3Schools is visited primarily by techies. RezHub has more of a mainstream flow of visitors. Finally, while my blog tends to lean towards the techie visitor, it does have a mix of both. Here is what I found…
W3Schools
W3Schools has a very techie following, meaning that most of their visitors have a technical background of some kind. They either are professionals in the IT industry, or they dabble in it in some way. That being said, most techies tend to use the most trendy applications and gadgets. As of today, the W3Schools website is showing the FireFox accounts for 47.7% of their visitors, and Internet Explorer collectively shares 41% across its various versions.

RezHub.com As I mentioned before, RezHub is frequented by a more mainstream web audience. There are all types and ages of people that come to this website, and has a very high number of unique daily visitors. It is a very clear indication of what the general public is using to browse the Internet. However, contrary to the techies, a mainstream Internet visitor is much less likely to change the web browser that they are using due to all kinds of reasons. Mostly, Internet Explorer is generally pre-installed and set as the default web browser of nearly all computers.

In what appears to be a drastic reversal in market share for the web browsers, RezHub’s visitors clearly favor the Internet Explorer family of web browsers at 64.48% of the visitors, while FireFox makes up a measly 24.74% of the market share.
My Blog: The Mighty Blog Now, we look at the favored web browser of my visitors here on this blog. The results look very similar to W3Schools, in that the trend clearly leans to the FireFox web browser at 45.52%, whereas Internet Explorer comes in second this time with 40.59% of the market share. Contrary to my original beliefs, it would appear that most of my visitors are also techies. I guess I need to post more food reviews, and some more of my photo work. :)

In Conclusion
Most of you were probably reading this to get an idea of which web browser(s) you should be covering more thoroughly in your development efforts. There appears to no longer be a conclusive stat that covers all demographics like there used to be in the IE 5 days.
We need to more closely consider our audience that we intend to visit our website than ever before. For example, if we were building a site that is targeted at delivering technical content to our visitors, we would probably want to make sure that FireFox renders the best out of all of the web browsers. In contrast, maybe a website whose purpose is to deliver cooking recipes would target Internet Explorer as their primary web browser.
In my own personal opinion though, you should be targeting both Internet Explorer and FireFox simultaneously. Even if your visitors are clearly using one web browser over another, you want to deliver the best possible experience to your visitors. This holds true for all use cases, including those where your visitors are not purchasing a product, but rather are receiving free content. If you have a competitor whose site functions and looks better in their favorite browser, you’re going to lose that visitor.
Let’s face facts, all sites exist to either earn money or traffic (usually both). Ignoring either major web browser will certainly lead to you losing visitors from the other browser demographic. I say develop for both, and this will also ensure a more stable future. You never know when and how fast one web browser will steal loyalty from the other.
Technorati Tags: Web Browsers,Browser,Market Share,Internet Explorer,IE,FireFox,FF

Unpacking Compressed JavaScript Code

wills@strohlsitedesign.com — Tue, 23 Jun 2009 15:31:00 GMT

I am working on a project where we have an outside party developing a DotNetNuke® module for us that relies almost entirely on client side code. When I way client-side code, I mean JavaScript, the jQuery library, and various jQuery plug-ins. The module itself is really a beautiful thing. It is actually able to be used outside of DNN without any problems at all.

Well, like any other project in the history of time, things go wrong. This time, I need to troubleshoot part of the the JavaScript chain of code to find out where an object is not getting reassigned. However, the JavaScript code is all compressed using the JavaScript Compressor online utility (based on the Packer by Dean Edward). What does that mean? That means that instead of having line breaks and indents throughout our client-side scripts, they are all removed, along with any code comments. This can significantly reduce page load times, and decrease the time it takes for the page to render in the browser as well. Not to mention that you’d save a ton of bandwidth.

So, instead of something like this:

/*

Some header comment here

*/

var will = 'awesome';

function awesomeness() {

if (will == 'awesome') {

alert('Will is totally wicked awesome!');

}

}

jQuery(document).ready( function() { awesomeness(); } );

You would see something like this:

var will='awesome';function awesomeness(){if(will=='awesome'){alert('Will is totally wicked awesome!')}}jQuery(document).ready(function(){awesomeness()});

For a JavaScript library or file containing hundreds or thousands of lines of code, you should be able to quickly see how effective this would be overall on a busy website.

Ideally, you would have two copies of every JavaScript file during development. The first file would contain the regular JavaScript, with all of its comments, indentions, line breaks, and so on. The copy of this file would contain the compressed version of the same code. Typically, the files would be something like: YourCompany.js, and YourCompany.compressed.js.

The problem I ran into today, was that our original JavaScript file did not contain the same code that was in the compressed version. To make matters worse, the compressed version of the code was the most recent version that I needed. Unfortunately, the JavaScript Compressor utility that we’ve been using does not yet employ a decompression or unpacking feature for code that was already compressed. That feature only exists for code that was compressed on the previous page load.

Our consultant is on vacation right now, and our client-side bug is live on our site, so please imagine how I panicked. :)

After a little while, and some diligent research, I happened across a blog post talking about “beautifying” JavaScript code. Basically, it was talking about the very thing I am talking to you about right now. It had the direct link to another free online tool. This one has the sole purpose of decompressing or unpacking JavaScript that was previously compressed like mine. Woo hoo!

Within a few clicks and seconds, I used the JavaScript Beautifier to make my JavaScript be human-readable once again. Awesome!

Technorati Tags: DotNetNuke,DNN Blogs,JavaScript

DotNetNuke Professional Edition’s Google Analytics Pro

wills@strohlsitedesign.com — Tue, 23 Jun 2009 11:46:00 GMT

I was one of the many people who watched Nik Kalyani’s first webinar, showcasing the anticipated Professional Edition version of DotNetNuke® version 5.01.00. As always, he did a fantastic job of presenting his topic to us. I really enjoy his talks. This blog is coming a bit late, as the webcast was last Wednesday.

I do want to calm any conspiracy theorists first though. The only affiliation I have with the DotNetNuke Corporation is that I am on the Media Module project team. They are in no way asking me to review DNN PE (which I do not have a copy of), and they might even be unhappy about it since they have a Marketing team who is dedicated to speak about such things. I am just like most of you. I am on the side lines, but unlike many of you, I am also a prospective customer. You may or may not know that my day job is as the Technology Director for RezHub.com. Our business relies 100% on DotNetNuke®.

In his talk, Nik highlighted both the Text/HTML Pro Module, and the Google Analytics Pro Module (GAP module) for DotNetNuke® version 5.01.00 PE. We will be talking about the Google Analytics Pro Module for right now. There are some slight differences between the Community Edition and Professional Edition of the Google Analytics module that DNN includes now. First of all, the module is indeed labeled differently in PE.

Google Analytics Pro" border="0" alt="DNN PE: Admin Menu > Google Analytics Pro" src="/Portals/1/Blog/Files/3/418/WLW-ReviewDotNetNukeProfessionalEditionWebin_95C2-dnnpe_admin_mega_menu_thumb.png" width="504" height="325" />

Once you choose the Google Analytics Pro page, the module interface is pretty simple. You can immediately tell though, that it includes some additional functionality that an Enterprise-level website would need. The Rules section below the Update button are not available in the Community Edition.

The Rules section allows an Administrator to very easily add Segmentation Rules to the GAP module. What are these for? Simple… They help a website administrator or a marketing team to better analyze traffic in a more granular way. Such a feature would only need to be available to a website team that had someone dedicated to this task. Generating the workflow, data, and analyzing that data is literally a full time job. That doesn’t even get us to the part of using the knowledge gained from that data.

If you simply add the Tracking ID that Google assigned to you and click Update, your HTML source will look the same as with any other Google Analytics (GA) solution that already exists.

Nik can certain explain it more eloquently, but adding the Segmentation Rules greatly increases your ability to track your visitors and customers. This tracking ability allows you to more efficiently determine things such as if your workflow patterns are working, where your conversion paths are failing, where your visitor came from, and where they left. There are so many more possibilities too.

In looking at Nik’s example, he was tracking visitors that were sent to the site from a trade show. He added a rule to track visitors who entered the site as a result of attending a trade show.

Segmentation Rules" border="0" alt="DNN PE: Google Analytics Pro > Segmentation Rules" src="/Portals/1/Blog/Files/3/418/WLW-ReviewDotNetNukeProfessionalEditionWebin_95C2-dnnpe_gapro_segementation_thumb.png" width="504" height="277" />

When the source for the site is view again, our HTML will have changed just a bit.

Segmentation Rules (HTML Source)" border="0" alt="DNN PE: Google Analytics Pro > Segmentation Rules (HTML Source)" src="/Portals/1/Blog/Files/3/418/WLW-ReviewDotNetNukeProfessionalEditionWebin_95C2-dnnpe_gapro_segmentation_htmlsource_3.png" width="333" height="144" />

This may not look so useful right now, but if you were to check your Google Analytics account after at least a day of this Segmentation Rule being rolled out, you will have a much more granular way to look at and analyze your website’s traffic. Think about it for a moment… All of the things that you already know and love about Google Analytics would still be available, and now you’d be able to look at the same information for a valuable subset of your visitors. I don’t know about you, but if my website is supposed to make money, that data is incredibly valuable to me.

Overall Impression

Just looking at what I have just showed you, the Google Analytics Pro Module may not excite you like it does me. However, I am not looking at this for my personal, small business, or catalog websites. I am looking at this from how such a feature would not only benefit me now, but also the upgrades to this core PE module going forward, should I make the switch to becoming a Professional Edition subscriber. Nik made it clear during the webinar that more features for this module are already in the road map that will take advantage of more of the Google API features.

I am impressed right now with their simple user interface. This is a necessity, especially for Enterprise customers. It seems that the more money a company makes, the less their staff truly understands software. At least, that’s been my experience. I think this module and the webinar in general both give us a very good peek into the future of DNN PE, in how they are approaching PE features.

I was going to post a link to the webinar for you to see everything for yourselves, but the webinar recording is not listed right now for some reason. I have a direct link to the WMV, but I do not think I am supposed to hand that out. Sorry… You can check out their webinars page to see if it gets posted.

I am excited to see more, and I am sure you are too, if you’ve made it this far into my blog post. Next, I will give you a peek at the Text/HTML Pro module. That is, as long as I do not get flogged for this post. ;)

Technorati Tags: DotNetNuke,DNN,DNN Blogs,Professional Edition,Review,Google Analytics,5.01.00

SmarterTools Software Bundles for Day of DotNetNuke Attendees

wills@strohlsitedesign.com — Mon, 22 Jun 2009 23:57:00 GMT

If you attended the Day of DotNetNuke® this year, you probably already know. If you don’t know, those who attended the event are getting a software bundle from SmarterTools, Inc. They were incredibly generous to us. They gave each attendee a license for each of their product offerings, which is a whopping $750 USD value for each attendee. The e-mails with all of the license information just went out.

Here are the software packages that each attendee is receiving:

SmarterMail Professional 5.x ($299.00 USD value) - SmarterMail 5.x Windows mail server is the cost-effective Microsoft Exchange alternative. SmarterMail provides antispam/antivirus out-of-the-box; reporting; events/notifications; throttling; email archiving; intrusion detection/prevention; advanced synchronization with Microsoft Outlook; and over-the-air support for BlackBerry, iPhone, and Windows Mobile devices. More info…

SmarterTrack 4.x ($199.00 USD value) - SmarterTrack 4.x brings the functionality of a help desk, Ticket system, Live Chat, WhosOn, branding and language support, cost analysis, data mining, reporting, surveys, and a Knowledge Base to a single Web application. WhosOn and Live Chat increase marketing performance and conversion rates, transforming a static Web site into an interactive marketplace. More info…

SmarterStats 4.x ($249.00 USD value) - SmarterStats 4.x is a Web log analytics tool that delivers detailed Web site statistics for a single site or up to 30,000 sites across a distributed network. SmarterStats supports multiple log file types (IIS, Apache, etc.) on Windows and Linux operating systems. SmarterStats also reduces disk space utilization up to 85% by converting log files into an efficient, relational database. More info…

PLEASE NOTE: The email generated by their system says that the software came from “DotNetNuke”, instead of “Day of DotNetNuke.”

In order to be eligible for this free door prize package, a few things had to be in place. If any break in this chain took place, then we couldn’t issue your license. Sorry.

Register for the Day of DotNetNuke®

Attend the Day of DotNetNuke® (we checked this through the registration desk at the event)

We need to have a valid e-mail address on file (walk-ins who didn’t give us their e-mail address cannot get the software package since we do not have an e-mail to send the license information to)

We plan to have a prize like this at every future Day of DotNetNuke®. So make sure you show up. :)

Thank you so much to SmarterTools for providing such a valuable prize! Also, they provided a really cool web service for me to plug into, that made issuing the licenses incredibly easy!

Technorati Tags: DotNetNuke,DNN,DNN Blogs,Events,Day of DotNetNuke

Remember Those DotNetNuke 5 Books?

wills@strohlsitedesign.com — Mon, 22 Jun 2009 20:36:00 GMT

The DotNetNuke Corporation is on the verge of releasing version 5.01.00 of the popular DotNetNuke® web application framework. I am so excited, because this is going to be the reason to finally jump aboard the version 5+ band wagon. Especially, when you include the fix they found for the high load performance issues from last week, this version of DotNetNuke® is going to be the best yet.

DotNetNuke® version 5.01.00 has all of the great things I love about version 5.00.00 and 5.00.01, but it is stable! Numerous bugs, performance updates, and workflow issues have been resolved. Among the new features to look forward to in version 5.01.00 are: Site Map Priorities, Human Friendly URL’s are turned on by default, a few SEO updates, more XHTML fixes, Module Definitions page displays if a module is in use, .Net framework 3.5 is required, there are event handlers for skins, a Google Analytics module, and much more. You can see for yourself what is in the DNN v5.01.00 release.

That is a whole lot of features… I certainly hope you’re as excited as I am! If not, maybe some books would help? It seems that since the first two iterations of the version 5 series was so riddled with bugs, everyone has all but forgotten some very important and useful DotNetNuke® books. The bugs and problems have been taken care of. Now you need to upgrade your sites. Version 5.01.00 is coming any day now. Here are the books I would suggest you pick up if you want to be proficient with the DotNetNuke® 5 series of releases.

Professional DotNetNuke 5 is the book that I had the pleasure of editing for technical content. With the exception of Shaun Walker, all of the authors are from Florida. I am so honored that I can call these guys friends. They all continually have done so much for the DNN community over the past 4+ years, and I wouldn’t be here without them.

I only had a hand in the module development chapters, but the entire book is great. I read it from cover-to-cover, and I don’t usually do that for any technical book. I gave this book a full review in my blog back in March. Rest assured, your money wouldn’t be wasted.

Professional DotNetNuke Module Programming is a book by the popular Mitchel Sellers. It’s no secret that he has a ton of DotNetNuke® knowledge. Luckily, we get the best DNN developer cheat sheet and resource, all wrapped into one with his book. This book tended to read more like a resource, versus the previous book. I wrote a full review of this book in a previous blog post.

The last book I will mention right now is one of which I poured a lot of time into, despite not being an author. I was the technical editor for the entire book. It really was a fun project.

The DotNetNuke 5 User’s Guide is written by Chris Hammond and Patrick Renner. It is not a book for any die-hard DNN’er, but rather the end-user who has just been introduced to DotNetNuke®. I think my favorite quote is from Chris himself. He mentioned that he wanted to write the book in such a way, that he’d be able to hand the book to his mother, and she’d be able to get her site up and running. I don’t have a review of this book yet, as I have not yet received my copy. I only have seen the chapters before the real editors got to them. From what I saw, Chris accomplished his mission. Buy one for your mother. ;)

As you can see to the left, this is the first Wrox book to sport their new design. I don’t know about you, but I like it. There was nothing wrong with the previous design, but this is nice too. :) Someone tell Amazon to update their book cover!

I hope you pick-up one of these books. They are all really great!

Technorati Tags: DotNetNuke,DNN,DNN Blogs,Book,5.01.00

Getting Rid of the Nasty BusinessControllerClass Exception

wills@strohlsitedesign.com — Mon, 22 Jun 2009 18:17:00 GMT

On many DotNetNuke® (DNN) websites you will find an unacceptable number of the following exception:

System.Exception: Error Creating BusinessControllerClass ‘YourModule.Modules.ModuleName.ControllerName’ of module(ModuleName) id=(ModuleID) in tab(TabID) and portal(PortalID) ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.

I have put the changing words in bold. Those words will be different for you.

This is almost always the result of the wrong business controller class being specified in the DNN manifest file. In the manifest file, the module developer will specify the business controller class so that DNN knows what Interfaces the module implements (such as: IPortable, and ISearchable). This is very important, because DNN will treat those module a little differently. For example, IPortable allows the module to be moved from portal to portal, very easily and all the while keeping the data from the original instance of the module.

Here is what is found in the manifest file for any given module:

<businesscontrollerclass>YourCompany.Modules.ModuleName.ModuleNameControllerbusinesscontrollerclass>

The problem I am speaking of is usually the result of a typo by the developer. Considering the previous example, you might instead see something like this:

<businesscontrollerclass>YourCompany.Modules.ModuleName.CompanyNameModuleNameControllerbusinesscontrollerclass>

Note that the company name is repeated in the controller name. This is not always the exact typo, but it is something that is easily fixed, regardless to why or how it happened. There are really two ways to get rid of this error:

Ask for an updated module release to fix this issue

Run a quick SQL statement to fix the error

The first option is obviously always the preferred method, especially to non-developers. Just tell the module developer/vendor that this error exists, and they should reply with a new release package. It’s very easy to do (provided they are not in the middle of a release cycle).

If you find that you either choose or want to fix this yourself, there is a very simple SQL statement you can run to do so. The first thing you need to do though is determine the actual business controller name and namespace. If this is not your own code, then you will have to use a tool like Visual Studio’s Object Browser. Using our previous examples, here is the SQL needed to fix this problem:

UPDATE [dbo].[DesktopModules]

SET [BusinessControllerClass] = N'YourCompany.Modules.ModuleName.ModuleNameController'

WHERE [BusinessControllerClass] = N'YourCompany.Modules.ModuleName.CompanyNameModuleNameController'

If you are using the DNN SQL module in your Host Menu, you might want to use this version of the previous T-SQL instead:

UPDATE {databaseOwner}{objectQualifier}DesktopModules

SET [BusinessControllerClass] = N'YourCompany.Modules.ModuleName.ModuleNameController'

WHERE [BusinessControllerClass] = N'YourCompany.Modules.ModuleName.CompanyNameModuleNameController'

That’s all there is to it… It’s fixed! It is not truly reflected in your DNN site and Event Log though, until the site cache refreshes. If you’re impatient, I have blogged about how to clear the cache in DNN before.

Technorati Tags: DotNetNuke,DNN,DNN Blogs,Event Log,Error,Exception

Review: Yabi Japanese Steakhouse in Winter Garden, Florida

wills@strohlsitedesign.com — Sun, 21 Jun 2009 05:20:00 GMT

I have been to quite a few Japanese steakhouses in my day. I really enjoy the atmosphere and the entertaining nature that they tend to provide. The cuisine is not so bad either. Today, I went to the Yabi Japanese Steakhouse in Winter Garden, Florida for the first time. It is new place that we happened upon this evening in looking for a good place for a pre-Father’s Day dinner. I gave the family one piece of criteria in choosing our dinner destination: It had to be a small business. No chains, or major brands.

Yabi Japanese Steakhouse
16112 Marsh Road, Winter Garden, Florida 34787
(407) 654-9588

The outside really did nothing to show the branding of the restaurant, or convey the feeling that an Asian cuisine lived beyond the front doors. Sometimes, this is the fault of the building owner though. You really cannot hold the restaurant responsible for that.

Upon walking in, the entrance and the rest of the restaurant has the minimum done to help convey the Asian atmosphere. I was definitely disappointed in that.

We sat down to order, and our server seemed nice enough. She knew and understood very little English though. She thought I ordered a Corona, when I actually ordered a Kirin Ichiban. And while I mention the Kirin, they are a whopping $4.50 each! Crap!

Their regular drinks such as sodas and tea are $2.00 each. That isn’t so odd these days, unfortunately, and it has prompted me to begin ordering a water with lemon at most places. However, this place doesn’t allow for free refills in a to-go cup. Once again, I was not impressed. Another bad first impression was my fork. It was all bent up. I am surprised it was laid out at all without being bent back into shape first.

Looking through the menu, the prices for all of the meals and appetizers seemed quite reasonable, in contrary to the drinks. I say reasonable, but they are at least comparable to other Japanese steakhouses. They had only a few options for vegetarians though.

We ordered an appetizer, sushi, and each had the hibachi or teppangaki table meal.

The appetizer came out pretty quickly. It was Sweet Potato Tempura ($3.95). Now, anyone who knows me, knows that I am not a fan for sweet potato at all. It’s one of those foods that I simply do not enjoy. However, knowing that I was going to review this later, I went ahead and tried it. I am so glad that I did. This was a fantastic dish! It was slightly crunchy on the outside, and sweet and tender on the inside. The deep frying technique and breading of tempura took away a little of the original sweet potato flavor that I do not enjoy, and enhanced it to a level of deep satisfaction and addiction. What I think really made it work for me was the mysterious sauce that was lightly drizzled over the top of it. Perfect!

Following the appetizer, our Japanese onion soup and salad was next to come. The salad was unremarkable. It was a standard garden salad with the ginger salad dressing. However, the soup was delicious. It was just the right blend of ingredients and broth. It had mushrooms, green onions, and fried noodles. We all liked it, and usually, I am the only one who likes the soup at these places.

I was quite disappointed in another area too. I always order sushi along with my hibachi meal. I have never had to wait on it until this time. It came when the first round of food was being served onto the plates at the table.

The sushi was delicious though. Every sushi place has one or more specialty rolls that are named for the area or region. This restaurant has a roll named the Winter Garden roll, named after the city it’s in. It was okay. Along with that roll, I ordered 4 pieces of Eel, 2 pieces of Salmon, and a Wasabi Roll. The Wasabi roll was fantastic! I really liked it. I would suggest it to any sushi lover. There was a few different types of fish in it. Something to note about the sushi that I haven’t seen before is that the menu itself was reusable. Instead of being a throw-away piece of paper, it was laminated to be reused. The order still gets taken on a normal piece of paper though.

Our teppangaki chef was also unremarkable. He started strong with some of the standard jokes and tricks. One thing he did that was new to me, was to break out a little fireman doll. When he pressed a button, it’s pants went down, and it peed oil onto the table which of course flamed up. It was funny. He faded very fast though, basically resorting to just cooking. He even failed to do the standard onion volcano. We had to point it out to the kids when we saw it at the other tables.

The meal he cooked up was delicious though. I ordered shrimp and scallops for myself, filet mignon for my lady, and the kids had chicken (1) and steak (2). The seafood all tasted very fresh. I also tried Kim’s filet, and it was definitely a high-quality cut of meat, cooked perfectly. We ordered the meat to be cooked medium. However, the popular white sauce was very runny, and not thick like I am used to.

In addition to the meats tasting great and being cooked perfectly, the vegetables and rice were also fresh and delicious. At the end of the meal, we were served chilled (near frozen) oranges. Like the rest of the food, they were fresh and delicious. They must have a really good produce supplier. (Other restaurants should take note.)

We found ourselves to be uncomfortable towards the end of our time there. When we first arrived, less than half of the restaurant was taken. By the time we were ready to go, people were standing in line, waiting for a table to open up. During that time, the side of the restaurant that had the teppangaki tables was extremely hot. We were literally sweating, and looking around, it was clear that we weren’t the only ones.

We cannot fully discuss any restaurant without also discussing cleanliness. The interior and exterior of the restaurant were very well kept. And the men’s restroom was also as clean as you’d expect a bathroom to be during the dinner rush. Nothing to report here.

So what’s my final verdict? There are definitely better places to go if you’re in the mood for a Japanese steakhouse. This one compares well in food quality and prices, but it really does fail in service. There were times when we could get any server, much less our own. I would tell you to find another place to get your hibachi grill craving taken care of. Your money is better spent elsewhere.

Personally, my favorite is Blue Fugu, in St. Pete Beach, Florida. Their website leaves much to the imagination, but they make up for it if you visit them. If you find yourself in their area, GO! You will not be disappointed – trust me.

Technorati Tags: Food,Review,Japanese,Steakhouse,Hibachi,Sushi,Restaurant

DNN Core Blog Module Stars in the next ODUG Meeting

wills@strohlsitedesign.com — Sun, 21 Jun 2009 01:58:00 GMT

One of the more misunderstood, and underestimated modules in the Core offering of DotNetNuke® Modules is by far the Blog Module. Everyone has an opinion on it, and most of us are wrong. Blogs are one of those adaptive concepts – it is what it is. A blog is one of those many, many things that simply give you back value based on what you put into it. Luckily, the latest release of the Blog Module makes that easier than ever before in DotNetNuke® (that is, without paying for it).

On July 9th, I will be presenting the DNN Core Blog Module for our next session at the Orlando DotNetNuke® Users Group, or ODUG. In this session, I hope to make the Blog Module understood by anyone that might be thinking about using it, or may have been confused about it in the past. Antonio Chagoury and his team have done a fantastic job at bringing this module up-to-speed to better compete with the other blog offerings out there, both on and off of the DNN platform.

We will walk through a first time blog configuration, and the flexibility it offers us to allow multiple blogs and blog themes. We will also take a look at the settings and options it gives us to truly make our blog our own. I have also done some things to help make my personal blog do some things that the Core Blog Module doesn’t do by itself. I will show you what I have done. Once we get through this, and if we have any time left, our final step will be to show you how you can modify the DNN Blog Module to put in some of your magic.

Be sure to attend this meeting. We will have some cool prizes, some Day of DotNetNuke® leftovers, and more. As always, our meetings are free, and we cannot guarantee that our live stream will be up and running. Make sure you show up. :)

Next ODUG Meeting: July 9th, 2009 [Register to Attend]

Technorati Tags: DotNetNuke,DNN,DNN Blogs,Blog Module,Events,Community,ODUG,Orlando DotNetNuke Users Group