SharePoint Thoughts

Tired of that Calendar Web Part taking up all your screen real estate, Kyle has a quick little tip on how to make the Calendar auto size.

http://www.thesug.org/blogs/kyles/Lists/Posts/Post.aspx?ID=14

This diagram outlines the flow of a HTTP request and the possible error codes you can get from a web server. Very helpful in outlining the processing of an HTTP Request.

View it here 2580 x 2023 pixels)

After Installing Microsoft Office SharePoint Server, the referenced SQL Server starts consistently dumping memory to the hard disk, and filling up the error logs with stack traces. Some symptoms of this before you check the SQL Server Error Logs may be, Read more

Microsoft announced the unveiling of Microsoft Search Server

The requirements for the servers are pretty beefy, but I’m going to get a beta up and running here soon.

Link to the Discussion thread on the Microsoft Services portal to discuss deployment and such. Read more

Webcasts from the tutorial, so you can download them locally:

1. Building the Product Config
2. Preparing the Basic Package
3. Protecting the Source Code
4. Setting Protected Environment
5. Try and Buy

The Related PDF

1. Tutorial

The SLP Video : Here

Out of the box, Dotfuscator Professional Edition Gold is designed to work with Microsoft SLP’s. It takes a little work to get it to work correctly, and for it to integrate nicely with Visual Studio 2005/2008.

1. Install Microsoft Software Licensing and Protection’s SDK from
   http://www.microsoft.com/downloads/details.aspx?FamilyId=7AE70AAA-8B7C-4E3A-AF83-B71B6877705B&displaylang=en Read more

It may be a little oblivious, but to get Software and Licensing Protection to work within Visual Studio, you need to reference the appropriate DLL. You’ll find the: Microsoft.Licensing.Runtime2.0.DLL in your “C:\Program Files\Microsoft SLP Code Protector” folder. You’ll need to copy this into the same directory as your solution file. Once you add this reference to your project, you’ll be able to use the Microsoft.Licensing namespace within your code.

So I kept running into this error on the SQL Server that I was working on, it kept filling up the SQL Server Logs as well as the Application Event Logs. I spent over an hour trying to find out what the problem was, I changed all the account information for the services that had that account as a services identity. I made sure the account was a server administrator, I made sure that the account was in the sysadmin role on the SQL Server, but alas none of this worked.  Read more

This is in reference to the following article:

Forms Authentication in SharePoint Products and Technologies (Part 1): Introduction
http://msdn2.microsoft.com/en-us/library/bb975136.aspx

A section of this article is incorrect, it tells you to add the following code to the connectionString section of the Web.Config

1. <connectionStrings>
   

2. <add name=”fbaSQL”

3. value=”server=spdb;database=aspnetdb;Trusted_Connection=true” />
   

4. </connectionStrings>
   

This is incorrect, the spot where it says value, should be connectionString as in the following codeblock Read more

For some reason, sometimes MOSS imports the same users twice and sometimes three times. I think it may have something to do with matching the users on incremental imports, but will need to test this theory further.

To fix this, you need to reset the index for the SharePoint Content source, after running a full crawl, you should only see a single entry for each user.