mylifeinaminute.com

I got a good chuckle out of this one.  Apparently Internet Explorer 7 cannot set a cookie for a domain where the domain name is composed entirely of UPPER CASE characters and the number of characters is odd. It’s a good thing they managed to fix that one.

Heather Solomon provides a “clean and condensed” style sheet for branding the default calendar in a WSS 3.0/MOSS 2007 site.  While Heather has provided a great starting point, her sample piece just was not looking right on a MOSS 2007 Enterprise farm I was working on.

I have updated Heather’s style sheet to cover any parts that her’s was missing (at least in Internet Explorer 7 and FireFox 2.0.XXX).

The updated CSS can be found here.

There may be times when you wish to present your users with personalized links or other types of information where their NT user id must be passed along/accessed in a form. One way to do this is with Javascript and ActiveX. I only recommend this method if you don’t have access to a master page or code behind to retrieve this information in a more traditional manner (i.e. “HttpContext.Current.User.Identity.Name” or the “SPUser” objects) AND this is being used in a controlled intranet scenario (i.e. all users are accessing your SharePoint instance with Internet Explorer).

You can retrieve the current logged in NT user name from a Content Editor web part with a combination of Javascript and ActiveX with the following:

<script type="text/javascript" language="javascript">

var objUserInfo = new ActiveXObject("WScript.network");
document.write(objUserInfo.ComputerName);
document.write(objUserInfo.UserDomain);
document.write(objUserInfo.UserName);

</script>

It is important to keep in mind that this method will not return any information from IIS or the current site being browsed, so the user name we retrieve within the ActiveX control has the potential to be different from the user name the user is currently logged in to the SharePoint instance with.

A reference to the “Wscript.Network” object can be found here.

Update: It appears that Explorer View does work, if Web Client (a Windows Service) is enabled. I do not have Office installed on the Virtual Machine (Windows Server 2003 R2) that I was testing IE 8 on, and as such there was no support for FPRPC (FrontPage Remote Procedure Call). In the future, I should use XP at the very least so I have FPRPC out of the box.  That, or I could just install Office 2007 on my test machines.

---

The Internet Explorer version 8 beta (download) was released on March 5th, 2008. I’ve had a chance to play with it in the office a bit, and while I think it’s (possibly) a step up from IE 7, it still has a long road ahead of it. In the course of testing the latest and greatest from Microsoft, I learned that the beta in it’s current form can not render an Explorer View of a Document Library in SharePoint (MOSS 2007 Standard). That makes it a show stopper for use at work, but here’s to hoping that it gets fixed sooner rather than later.