Wednesday, June 3, 2009

Thursday, May 28, 2009

Fixing “web page not available” in Chrome

I love Google Chrome, but at work I incessantly get “web page not available” errors. Usually refreshing the page (F5) will get it to load right, but I was getting sick of it and about to kick Chrome to the curb.

At first, I though it only happened on MSDN sites and it was a Microsoft conspiracy. However, then it started cropping up all the time.

Here’s a setting that I disabled that seems to help:

Options > Under the Hood > Uncheck “Enable phishing and malware protection”

I wouldn’t recommend this for most users, but we already have this type of protection through our corporate network.

Saturday, September 27, 2008

StackOverflow - My New Addiction

I can't stop going to StackOverflow. I think it's the combination of respecting the founders through their blogs beforehand, the use of reputation points to force you to get involved and the narcisissm of checking the views and votes to my questions and answers.

See, a question I asked recently got mentioned in an article about StackOverflow: http://tagedge.com/2008/09/24/stack-overflow/ (Guess which one.)

This is bad...

Wednesday, April 23, 2008

SPD: SharePoint Designer 2007 won't take my license key

I was banging my head on getting SPD installed. I tend not to think that the specific CD that I used would affect which key I should use. Silly me...

"SharePoint Designer 2007 (For Use with TechNet Media)"

Monday, April 14, 2008

SharePoint: Display site title

Normally, the site title is included in through a content placeholder.

<Title ID=onetidTitle><asp:ContentPlaceHolder id=PlaceHolderPageTitle runat="server"/></Title>

I needed on my master page directly though, since it wasn't always in every page layout.

<Sharepoint:ProjectProperty id="onetidProjectPropertyTitle" runat="server" property="Title" />

Wednesday, April 9, 2008

SharePoint: Batch file to deploy WSP

PATH "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\bin"
stsadm -o deactivatefeature -name SPRSS -url http://localhost
stsadm -o retractsolution -name SPRSS.wsp -immediate -url http://localhost
stsadm -o execadmsvcjobs
pause
stsadm -o deletesolution -name SPRSS.wsp
stsadm -o addsolution -filename SPRSS.wsp
stsadm -o deploysolution -name SPRSS.wsp -url http://localhost -immediate -allowGacDeployment -force
stsadm -o execadmsvcjobs
pause
stsadm -o activatefeature -name SPRSS -url http://localhost
pause

Monday, March 31, 2008

SharePoint: VSeWSS on workstation

Keywords: Visual Studio 2005 Extensions for Windows SharePoint Services 3.0 Tools, VSeWSS, VSeWSS.exe

Error Message:“This product can only be installed if Windows SharePoint Services 3.0 has been installed first”.

Regedit:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0]
"Sharepoint"="Installed"

I do not believe this works with VSeWSSv11.exe. You'll probably need to do this instead:

http://blogs.msdn.com/martinv/archive/2008/03/19/new-registry-file-for-developing-moss2007-projects-in-a-workstation-xp-or-vista.aspx