Another reason VB.Net is inferior to C#

A while back I developed a custom module in DNN for a client. Due to my desire to type as little as possible I used the letters from the client's name to create the namespace -- ASC. We had been running DNN 4.8 and all seemed fine until I was told to upgrade to 5.1 Somewhere along the line the DNN core code had been modified to make a call to a VB.Net method Asc. Since VB.Net is *NOT* case sensitive like C# this caused a host of problems - mainly, the site would not load and there was no kind error message informing me as to what had happened.

After rewriting and redeploying my DLL to use a different namespace all was right with the world, but I wasn't happy.

DNN and Fallback Skin Doctype

Recently I was required to upgrade a customer's DNN site from 4.8 to 5.0. Simple enough, right?
1) Copy site folder to another location
2) backup database
3) extract the contents of the upgrade zip file into the site folder
4) navigate to http://SITEURL/install/install.aspx?mode=install
5) VOILA! Upgrade complete

Unfortunately, after doing the upgrade the customer's dropdown menus were no longer appearing on top of the content (we had used CISS.SideMenu for the menuing system) . Upgrading the menu module only made things worse - the menu bar disappeared altogether. So, I reverted back to the 4.8 site and went about replicating their environment on a VM.

Thinking that maybe the problem was DNN 5.0 I decided to go straight to DNN 5.1. The upgrade was successful and in the process I was able to resolve another problem the customer was having - the dropdown menus look garbled in IE 8 unless the site was run in compatability mode. I was stoked and ready to tackle the production server again.

Much to my dismay, after the second upgrade went seamlessly, the same problem appeared. I was ready to throw in the towel. Thanks to a kind co-worker who jogged my memory I was able to resolve the problem.

I had changed the Fallback Skin Doctype on the portal settings screen to XHTML 1.0 transitional on my VM AND on the production server BEFORE doing the upgrade (http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryId/2130/The-Fallback-Skin-Doctype-and-skinning.aspx). This had been done in an attempt to resolve the IE 8 issue. Unfortunately, the upgrade to 5.1 wiped out this setting. Once I changed it back the menus appeared just fine.

The Dreaded "The SSP Timer Job Distribution List Import Job was not run."

Unfortunately, when I set up some test SharePoint sites on my dev machine I tied service accounts to my network userid & pwd. Our network policy requires that passwords be changed every 90 days, so every 90 days I get into a pickle because I can't remember all that I had to do so that SharePoint would continue to play nice on my machine.

1. In IIS, change the password of all App Pools that are tied to my network account and restart IIS


2. At the DOS prompt run stsadm -o updatefarmcredentials -userlogin <domain\userid> -password <new password> followed by iisreset /noforce


3. In Central Admin:
   
   • Go to App Management and click on "Manage Search Service" under the "Search" group and change the "Office SharePoint Search Indexing and Query" account's password
   
   
   • Click on Shared Services Administration, right-click the default shared service and select Edit Properties and update the password for the SSP Service Credentials


4. At the DOS prompt run iisreset /noforce

How to Show/Hide SharePoint QuickLaunch

The bulk of this comes from http://suguk.org/blogs/sharepointhack/archive/2008/01/29/8093.aspx

Insert the following JavaScript block immediately before the </Head> tag in your master page:


<!--
function showhide(layer_ref)
{
var state = 'block';

var tbl = document.getElementById(layer_ref);
var img = document.getElementById("img" + layer_ref);

if (tbl.style.display == 'block')
{
tbl.style.display = 'none';
img.src = "_layouts/images/BLK_RGT.GIF";
}
else
{
tbl.style.display = 'block';
img.src = "_layouts/images/BLK_LEFT.GIF";
}
}
//-->
</script>

I put the following div immediately inside the TD with ID LeftNavigationAreaCell:
<div id="divOuterQuickLaunch" style="display:block;">

I added the following immediately after the ContentPlaceHolder PlaceHolderTitleAreaSeparator:

<tr>
<td style="text-align:right;">
<a id="lnkregionalNav" style="cursor:hand" onclick="showhide('divOuterQuickLaunch');">
<img src="_layouts/images/BLK_LEFT.GIF" id="imgdivOuterQuickLaunch" alt="Show/Hide Quicklaunch"/>
</a>
</td>
</tr>


If you are looking at a list, the behavior will not be as expected as there is an image at the top of the page that prohibits the quicklaunch area from collapsing when hidden. To correct this, find the ContentPlaceHolder PlaceHolderPageImage and add Visible=”false”

That should do it.

How To: Associate a K2[blackpearl] SmartObject with a SharePoint list

This PDF describes how to associate a K2[blackpearl] SmartObject with a SharePoint list:

How To Associate a K2[blackpearl] SmartObject with a SharePoint list

How To: Create a custom Google map icon

I had found some very valuable resources when I was starting to develop Google maps:

The Google Maps API Reference http://code.google.com/apis/maps/documentation/reference.html

Google Maps API Tutorial http://econym.googlepages.com/index.htm

For specifically creating custom Google maps icons http://googlemapsapi.blogspot.com/2007/04/labeledmarker-v10-do-more-with-your.html

As valuable as those references are I often had a lot of hit and miss trying to get the various pieces to work together. I hope this blog will help someone see how the various pieces get stitched together.

A JavaScript function to create the marker and set up the event window

// point = new GLatLng(lat,lng);
// infoWindowText = text to be displayed in the info "balloon"
// type = which icon to use
// count = which item in the group we are processing (e.g. item 16 out of 120 total) 
function createMarker(point,infoWindowText,type,count) {
          var xOffset = -1;
          var yOffset = -29;
         
// to get the number to appear within our mappin, the xoffset
// had to be adjusted depending upon what numbered item the
// current location is within our result set
          if(count > 99)
            xOffset = -7;
         
          else if(count > 9)
            xOffset = -4;
         
          bounds.extend(point);
          // need to create 1icon for each number will have
// GIcon is explained at http://code.google.com/apis/maps/documentation/reference.html#GIcon
            var Icon = new GIcon(baseIcon);
// background is a previously defined array of icon "types", each of which points to its own
// specific .gif
// e.g. background["Gold"]  = "../images/mappins/lorange.png";
            Icon.image = background[type];
            opts = {
              "icon": Icon,
              "clickable": true,
              "labelText": parseInt(count)+1,
              "labelClass": "MapIcon",
              "labelOffset": new GSize(xOffset, yOffset)
            };
// LabeledMarker is explained at http://googlemapsapi.blogspot.com/2007/04/labeledmarker-v10-do-more-with-your.html
        var marker = new LabeledMarker(point, opts);

// openInfoWindowHtml is explained at http://code.google.com/apis/maps/documentation/reference.html
// this tells the screen to display an info "balloon" when the user clicks this point on the map
            GEvent.addListener(marker, "click", function() {
            marker.openInfoWindowHtml(infoWindowText);
        });
        i++;
        return marker;
       
      }

in the main Javascript code you will have the following

// create the marker
var marker = createMarker(point,name,html,type,i);
// addOverlay is explained at http://code.google.com/apis/maps/documentation/reference.html
// adds the newly created marker as an overlay on the map
map.addOverlay(marker);

How To: Associate a custom action with a specific SharePoint list

There are many web sites that discuss how to associate a custom action with a specific SharePoint list. The ones that helped me the most are:

• http://www.eggheadcafe.com/software/aspnet/29397132/how-to-only-apply-a-custo.aspx (includes the default SharePoint ContentTypeIds)
• http://johnholliday.net/resources/customactions.html (contains the Custom Action identifiers – what to use for GroupId and Location settings)
• http://sharepointinsight.com/blog/Lists/Posts/Post.aspx?ID=33 (pretty good step-by-step instructions)
• http://www.thesug.org/blogs/moss-pit/Lists/Posts/Post.aspx?List=db170c8d%2Daeb1%2D448b%2Dbe4b%2Da863c08b4816&ID=11

For whatever reason, I was still having problems getting it all to gel together when trying to apply custom actions to the EditControlBlock for a new list feature that I had created. To help me remember for the future, I thought I would recreate the steps here.
When creating my list template, I used the Sharepoint Solution Generator (available for download here: http://www.microsoft.com/downloads/details.aspx?familyid=7BF65B28-06E2-4E87-9BAD-086E32185E68&displaylang=en)
In the ListDefinition.xml and schema.xml files I set the Type attribute to a large number as explained in the sharepointinsight.com link above. In my case, I set the value to 22222. I then deployed my custom list to my SharePoint site.

To create the custom menu items specific to my newly created feature:

1. I started by creating a new folder in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES.

2. I then copied the Feature.xml and ListTemplates\CustomList.xml from C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\CustomList into my new folder.

· In my case, I did not put the CustomList.xml file in a sub-directory but left it at the same level as the Feature.xml file.

· You should rename the CustomList.xml file to a name corresponding with the new list that was created (ex. NewListNameListFeatures.xml)

3. I modified the Feature Title, Feature Description and ElementManifest Location attributes in my Feature.xml to be specific for my list feature

· The ElementManifest Location attribute must match the filename specified in step 2

4. In the CustomList.xml file, renamed of course, I entered the following (click the image for a larger view):

For this specific scenario to work, some items of note are:

· The RegistrationId attribute must match the “Type” value used when creating the custom list.

· The Location attribute must be “EditControlBlock” for the new menu item to appear in the per-item edit control block menu

· There is no GroupId attribute if Location is EditControlBlock

· The RegistrationType attribute must be “List”

· I didn’t see anything specific about what the Id attribute should be, I simply used a naming convention of ListName-and-Action.

· The UrlAction Url attribute can be JavaScript instead of an actual url (e.g. Url="javascript:window.open('http://www.google.com');".

5. I then installed and activated my custom action using stsadm:

· stsadm -o installfeature -name <folder where custom action resides>

· stsadm -o activatefeature -name <folder where custom action resides> -url <my SP site url>

· iisreset

Voila! My list now has a new item in the edit control block menu.