Friday, 13 February 2009

Create custom 404 in MOSS 2007

http://support.microsoft.com/kb/941329/en-us

We had an issue where our new site had the same Url as the old one and Google search results were returning the old one which was no longer visible (Url pointing to new IP address) the above link is to the Microsoft Knowledge Base article for a solution. It worked for us.

Tuesday, 10 February 2009

Entity Framework

Finally got the EF to install!! It appears that VS2008 did not have SP1 and non of this was picked up on the updates. Once installed the DataModeller appered

Monday, 9 February 2009

Entity Framework Tests

Just a quick one – guess I was being an idiot (no change there then). I was creating a couple of tests for my entity model and got an error

"The specified named connection is either not found in the configuration, not intended to be used with the EntityClient provider, or not valid."

A little bit of searching revealed that I needed an app.config for the test project with the connection settings for the model – makes sense but was confusing at first.

Entity Framework

Had some problems, and still do, installing the Entity Framework on my home laptop. At one point after un-installing 3.5 SP1 and the updates VS2008 decided that it would also delete all my templates.

Tuesday, 27 January 2009

IE8 RC1 Released

It has been announced that IE8 has gone to RC1. See the notes for known issues

http://www.microsoft.com/windows/internet-explorer/beta/worldwide-sites.aspx

Wednesday, 21 January 2009

Content Deployment Manifest Reader

I found this tool from Maxime Bombardier about troubleshooting content deployment issues along with a link to an excellent tool for debugging the manifest file to see where the content deployment is failing.

http://blogs.msdn.com/maximeb/archive/2008/05/16/sharepoint-content-deployment-manifest-reader.aspx

Thursday, 15 January 2009

Remote debugging

I was looking at a way to get remote debugging working for debugging MOSS custom webparts from an VS2008/XP PC to the Win2003 server running MOSS.

The section “The Remote Debugging Monitor is the one accepting your debug calls and the talking back to Visual Studio on your client, so to get these things to work you have to start the client as the user running Visual Studio (or have administrative permissions on the client). You can either log in to the remote host using that user or, as I prefer, right-click on the msvsmon.exe and choose Run As... Make sure that the user you are using to run the monitor with is member of the local Administrators group.” was a ‘gotcha’ that I missed first time round.

http://www.wictorwilen.se/Post/How-to-get-Remote-Debugging-work-properly.aspx

Do remember that when you attach to the w3p process during debugging it will prevent other users on MOSS from performing any actions.