Ben There, Done That

So this weekend I decided to install SharePoint 2010 on my desktop at home.  My desktop is running Windows 7, and due to requirements of other software I need, I’m unable to run Windows Server 2008 on it.

Running a stand alone installation of SharePoint 2010 is great, however, I wanted to see if I could get a complete install on Windows 7 and user SQL Server 2008.  Fortunately, I found this blog post by Neil Hodgkinson that explained how to do it.  Everything appeared to be working great and the configuration wizard finished without any problems.  Unfortunately, that appearance didn’t last too long.

My problem arose when I went into Central Administration and, despite being a farm administrator, the first thing I noticed was I couldn’t create new web applications.  There were some other security issues as well, however, those are beside the point.  The purpose of this post is how to go about fixing this issue if you encounter the same thing.

After mulling over the issues for a few minutes, I remember are beloved User Access Control (UAC) and other issues I’ve seen when it is enabled on Windows Server.  So, I went into my UAC settings, disabled them complete, restarted my computer, logged into Central Administration and what do you know, it worked!  I can now create new web applications and have full control over my SharePoint 2010 installation.

Ben SharePoint 2010 SharePoint, SharePoint 2010, UAC, Windows 7

As discovered by Todd Carter there is a memory leak in SharePoint 2007.  He has outlined the details as well as a work around to the fix the memory leak.

I decided to do some testing with it, however, when I compiled the dll, placed it into the GAC, and changed my global.asax file, I started getting this error: “Could not load file or assembly ‘[Assembly Name]’ or one of its dependencies.  The system cannot find the file specified.”

After digging into this error for a while I discovered my problem.  This may be fairly obvious to developers out there , but coming at this from more of a SharePoint administrator type roll, I missed this one step that isn’t outlined in the steps provided by Todd.

After deploying your dll to the GAC, you need to open up your web.config and place

<add assembly="[Assembly Name], Version=[Version Number], Culture=neutral, PublicKeyToken=[Public Key Token]" />

in the web.config file of the web application you wish to apply your fix to.  This line should be added between <assemblies> and </assemblies> in the web.config file.

All of the information: Assembly Name, Version Number and the Public Key Token can be found by right clicking on your dll in the GAC and viewing the properties of the dll.

Once I added the assembly to my web.config for the web applications I was trying to apply the fix to, everything worked as expected.

Ben Customizations, Development, SharePoint, SharePoint 2007 Development, Errors, Memory Leak, SharePoint, SharePoint 2007

A while a go a write a short post on how to hide web part headers in SharePoint 2007.  Recently I had some inquire how to do the same thing for SharePoint 2010.  So, here is what to do in order to hide a web part header in SharePoint 2010.

1.  Add a content editor web part to your page.

2. Edit the Web Part

3. Click in the content area of the web part, click HTML and select “Edit HTML Source”

4. Put the following code in the web part:

5. Click “OK”

6. Expand “Appearance” (on the right side of the page)

7. Set the chrome type to “None”

8. Click “OK” and then save and check in your page.

The headers of your web part should now be hidden.  This can be extremely helpful when your page contains a web part using “boxed” for your style when creating a list view.  The only downside to this approach is if you have multiple web parts on a single page, it will hide the headers for all the web parts on your site.

How to do the same thing in SharePoint 2007

Ben Customizations, Development, SharePoint 2010 Content Editor, SharePoint, SharePoint 2010