icebrrrg.com

Arrgh. I’ve spent the last two days wrasslin’ with the idiosyncrasies of Sharepoint / MOSS 2007, trying to deploy the Microsoft Enterprise Library / Logging Application Block. I’d chosen the tool to “save time” (ha!) in developing a reusable logging tool, that can log to the EventLog, a flat file, a DB, etc etc … and it works great. But good luck trying to get it to work in a SmartPart or web part or user control in SharePoint.

Or, read on.

Basically you have to get SharePoint to see the assemblies. I’m using the Enterprise Library 3.1 (May 2007). So I installed the download on the SharePoint server (you may be able to just copy the assemblies you need, but what the heck). Then I copied the DLLs that the web controls reference from the Enterprise Library’s /bin folder into the GAC (you should know how to do this), making note of the PublicKeyToken, version numbers, etc.

The hairy part was figuring out what exactly needed to go into the SharePoint site’s web.config file (located in %wwwroot%/wss/VirtualDirectories/80). Here’s what I had to add, and where:

<configuration> <configSections>  <section name="loggingConfiguration"   type="Microsoft.Practices.EnterpriseLibrary.Logging.Configuration.LoggingSettings,   Microsoft.Practices.EnterpriseLibrary.Logging, Version=3.1.0.0, Culture=neutral,   PublicKeyToken=b03f5f7f11d50a3a" /> </configSections> <SharePoint>    <SafeControls>   <SafeControl Assembly="Microsoft.Practices.EnterpriseLibrary.Common, Version=3.1.0.0,    Culture=neutral,    PublicKeyToken=b03f5f7f11d50a3a"    Namespace="Microsoft.Practices.EnterpriseLibrary.Common" TypeName="*"    Safe="True" AllowRemoteDesigner="True" />   <SafeControl Assembly="Microsoft.Practices.EnterpriseLibrary.Logging, Version=3.1.0.0,    Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"    Namespace="Microsoft.Practices.EnterpriseLibrary.Logging" TypeName="*"    Safe="True" AllowRemoteDesigner="True" />   <SafeControl Assembly="Microsoft.Practices.ObjectBuilder, Version=3.1.0.0, Culture=neutral,    PublicKeyToken=b03f5f7f11d50a3a" Namespace="Microsoft.Practices.ObjectBuilder" TypeName="*"    Safe="True" AllowRemoteDesigner="True" /> </SafeControls>  </SharePoint>  <system.web>    <securityPolicy>      <trustLevel name="WSS_Medium"    policyFile="C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12configwss_mediumtrust.config" />      <trustLevel name="WSS_Minimal"    policyFile="C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12configwss_minimaltrust.config" />    </securityPolicy>    <compilation batch="false" debug="false">      <assemblies>  <add assembly="Microsoft.Practices.EnterpriseLibrary.Common, Version=3.1.0.0, Culture=neutral,   PublicKeyToken=b03f5f7f11d50a3a" />  <add assembly="Microsoft.Practices.EnterpriseLibrary.Logging, Version=3.1.0.0, Culture=neutral,   PublicKeyToken=b03f5f7f11d50a3a" />  <add assembly="Microsoft.Practices.ObjectBuilder, Version=1.0.51206.0, Culture=neutral,   PublicKeyToken=b03f5f7f11d50a3a" />      </assemblies> </compilation>    <trust level="WSS_Minimal" originUrl="" />  </system.web> <loggingConfiguration name="Logging Application Block" tracingEnabled="true" defaultCategory=""  logWarningsWhenNoCategoriesMatch="true"> {copy this from your VS.NET web.config} </loggingConfiguration></configuration>

Hope this helps you … please not that this is not a complete web.config, it’s just the new bits that need to be added.

After that, an iisreset, and things were kickin’. YMMV.

Do you ever wonder what I do for a paycheck? Well, I sell and support and design software that works with voice over IP (VoIP). I work with Cisco technologies for the corporate world, mostly (not consumer VoIP like Skype and Vonage). As you may or may not have seen, if you’re a TV junkie, Cisco’s voice and video toys have been featured in great TV shows like Alias, 24, Las Vegas, and most recently Grey’s Anatomy. Man I love that show.

Anyway … some new Cisco tech (that I play with, and have beta tested) is in the season finale of 24 this year. It’s featured hardcode. Want to see the video excerpts? No spoilers, I promise! You get to see the tech I sell and play with every day.

This morning I had limited time between meetings, and had to dial into a national conference call. I hopped onto the T-Mobile hotspot at the Starbucks, and joined into the web portion of the call … and dialed into the voice portion via Skype! I skype all the time, so this is not real news, but this is the first time I’ve done it in an untested hotspot. The audio was awesome, with my Plantronics Digital DSP 400 headset. This thing is friggin’ awesome. It’s got its own external DSP so it doesn’t drain resources on the laptop, and it has an external volume and mute control … plus it’s USB. So I was on this call via Skype and this headset, talking to all the movers and shakers in North America, and no one could tell. Kudos to the engoineers!

What’s more, Skype has just announced free calling outbound to numbers in the US and Canada. Yeah, free. Have you ditched your landline yet?

welcome to the first-ever blog on icebrrrg.com. i’m using the gui from blogger.com, which is okay but lacks lots of bells ‘n whistles. i’m hoping to get a blogger module for my site once i dotnetnuke it … more on that later. still waiting on word from the lovely folks at ngen, to see if i can get a db for the site!

this blog is a work in progress and may move around, look different, etc. please excuse our mess.