Office 2010 RTM 32bit vs 64bit Versions

As we’re all aware of by now Office 2010 has been released to manufacturing which has it and SharePoint 2010 becoming available to MSDN & TechNet Subscribers. On first impressions this version has been pretty good, I’ve been running the beta client pieces for the last 6+ months. It seems there’s a little confusion that has slipped in with this release though as for the first time we have both 32 and 64 bit versions of this release. If you’re like me and running 64bit OS (Win 7 in my case), because you need more than 4Gb of RAM.

A trap that I found out from Ben Walters presentation at this months MOSSIG meeting was that Microsoft’s recommendation is to use the 32 bit version of Office 2010 even on a 64 bit Operating System, unless the user needs to manipulate large files, which I’m guessing is over 4Gb given that’s the 32 bit memory limit. Another interesting point for this was also that the plug-ins are going to be harder to get in 64 bit which probably a fair point. This little gotcha isn’t very well publicised but I found this line of text “In enterprise environments, the default is to install Office 2010 32-bit on computers that run either 32-bit or 64-bit editions of Windows operating systems. We recommend this option.” which I found within this TechNet article.

Anyway time to uninstall 64 bit and go back to 32 bit.

Advertisements

Missing Details, Thumbnails & Filmstrip views in Picture Libraries

I found a some very strange behaviour on client installation where suddenly the Details, Thumbnails & Filmstrip views had vanished from a Picture Library.

This is the way a picture library usually looks :-

image

This is the way my picture library is looking now:-

image

My initial thought was that I’d broken something through the site customisation of the minor Master Page tweaks and some style tweaks, but what when I packaged up the work and deployed to another server I saw that it all worked and appeared to be a server wide issue.

This blog post has confirmed where the issue had come from. The Infrastructure Update for WSS and MOSS  had caused the issue, Microsoft are aware of it and are currently working on a fix, I’ll let you know when I hear more. There is currently no known work around for this issue.

Posted in MOSS. 1 Comment »

MOSS Daylight savings time Update for Australia 2008

Seems like the daylight savings issues are continually biting. On the bright side the fix this year for MOSS is a very simple xml change. Simply navigate to “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\CONFIG” and edit “timezone.xml”. I’d recommend making another copy of timezone.xml at this point just in case. The example here fits for East Coast Australia 2008. Simply go through file until you find your particular timezone, then modify the values or Month Day Hour, just remember that Day is actually the week that it changes ie in this example DST starts in the first week of October this year in Melbourne. It’s all pretty straight forward.

<TimeZone ID="76" Name="(GMT+10:00) Canberra, Melbourne, Sydney" Hidden="FALSE">
  <Bias>-600</Bias>
  <StandardTime>
    <Bias>0</Bias>
    <Date>
      <Month>4</Month>
      <Day>1</Day>
      <Hour>3</Hour>
    </Date>
  </StandardTime>
  <DaylightTime>
    <Bias>-60</Bias>
    <Date>
      <Month>10</Month>
      <Day>1</Day>
      <Hour>2</Hour>
    </Date>
  </DaylightTime>
</TimeZone>

Posted in MOSS. 3 Comments »

Item-level permissions on document libraries.

I recently had a client requirement where the client wanted to created a “drop box” type of document library, where users were able to modify and view only there own documents. I knew this possible in custom lists through this option being displayed in List Setting / Advanced Settings link.

Only Their Own settings

What I didn’t realise was that this option wasn’t displayed in document libraries. I found this post from Matt Morse that had the solution to this problem. Matt points out that when you take a look in the Microsoft.SharePoint.ApplicationPages.dll the following code exists in the AdvancedSettingsPage class’s OnLoadEvent.

this.ItemLevelSecurityPanel.Visible = (type != 1) && (type != 5);

Where type is the base type of the list (1 = doclib, 5 = issues)

The Fix

Matt has written a great little tool here, and the source is available here. The code is pretty straight forward as you can see from the snippet below.

    SPSite site = new SPSite(siteUrl);
    SPWeb web = site.OpenWeb(webUrl);
    SPList list = web.Lists[listName];

    PropertyInfo pInfo = list.GetType().GetProperty(propertyName);

    if (pInfo.PropertyType == typeof(int))
        pInfo.SetValue(list, Convert.ToInt32(propertyValue), null);
    else
        pInfo.SetValue(list, propertyValue, null);

    list.Update();

    web.Dispose();
    site.Dispose();

The property that we are setting in this case is ReadSecurity and WrtieSecurity the possible values are documented in these MSDN pages. In my case I was setting “Users have read access only to items that they create (2)” and “Users can modify only items that they create (2)”. Using Matt’s tool I basically just entered the following from the command line.

SPSetListProperty “http://server” "/Site" "Document Lib" "ReadSecurity" "2" 
SPSetListProperty “http://server” "/Site" "Document Lib" "WriteSecurity" "2"

Once this was done the document library performed exactly how we required, now the users who have contribute permissions can use this library to view and edit only their own items, and owners are able to see all items in the document library.

Posted in MOSS. 2 Comments »

Installing Telerik MOSS Editor

I’ve been working for a client where they have decided to implement the Telerik MOSS RadEditor. The editor definitely makes some great advancements against the default editor that comes out of the box with Sharepoint. Probably in my rush to get this installed and operation I missed some steps, so I thought I’d run through some of my experiences in getting this working.

  1. Download and install the ASP.Net Ajax Extensions from here this will need to be installed on all front end servers, although I’d recommend doing this on all servers in a farm in case there’s a need to redeploy servers later.
  2. Enable Ajax on all the Sharepoint front end servers. Again I’d recommend doing this to all servers. The instructions can be found on Mike Ammerlaan’s blog, here. A word of warning here these steps are pretty messy, and involve manually editing the web.config in several places. I’d strongly recommend that there is a backup copy of the web.config made before you start changing this file so that you can easily roll back in case something goes wrong, especially in production environments. You may also want to consider writing a Nant or MSBuild script to repeat these steps, especially if you are deploying into a large farm environment.
  3. Once the first 2 steps are completed the rest of the installation is pretty straight forward by adding the solution to the server in your farm which contains Central Admin. Simply follow the steps on Telerik’s site here.
  4. One last step that isn’t documented is to do an IISRESET following the deployment of the solution. Not sure exactly why but I couldn’t get it working without this magic last step.

VS 2008 Support for WSS in VSeWSS version 1.2!

The Sharepoint Team Blog have just announced Version 1.2 of the Visual Studio Extensions for WSS, which now supports Visual Studio 2008. This new version is only work with VS 2008, so if you’re still working with VS 2005 you will need to stick with Ver1.1.

Version 1.2 can be downloaded from here.

Windows SharePoint Services 3.0 SP1 on Vista x64/x86

This is some great news, one of my biggest criticism of SharePoint has always been the fact that you need a Server to run it on, even just for development. I’ve managed to work around this with lots of ram a collection of VPC’s with diff disks. But it looks like it’s been solved here. I’m going to be trying this out this afternoon. The next question will be if the Visual Studio WSS Extensions work with it, as they won’t install on a machine where it doesn’t detect SharePoint installed.