Site Sections
Posts
250
Comments
24
Trackbacks
13
November 2009 Entries
SharePoint 2007 and InfoPath 2010 Client – current install issues…

Ok, I’ve been bitten twice in the past week on this.  If you have InfoPath 2010 Beta installed and you’ve also got SharePoint 2007 running, at least with the latest SP2 and October CU, you run into an issue that surfaces in the logs as follows

One or more types failed to load. Please refer to the upgrade log for more details

When you pull that log apart, you’ll see that it’s attempting to load a few types such as Microsoft.Office.InfoPath.Server.DocumentLifetime.XmlFormHost' from assembly 'Microsoft.Office.InfoPath.Server.

Which, they fail – removing InfoPath from the install works.

posted @ Tuesday, November 17, 2009 6:24 AM | Feedback (0)
Loopback Check on Windows 2008, etc.

This KB article (KB926642) explains 2 methods for handling the scenarios that we as developers require for using a local machine for development.  My option has been, going forward, of being explicitly in the host names that my development machine will use.  From that article:

Method 1 (recommended): Create the Local Security Authority host names that can be referenced in an NTLM authentication request

To do this, follow these steps for all the nodes on the client computer:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
  3. Right-click MSV1_0, point to New, and then click Multi-String Value.
  4. In the Name column, type BackConnectionHostNames, and then press ENTER.
  5. Right-click BackConnectionHostNames, and then click Modify.
  6. In the Value data box, type the CNAME or the DNS alias, that is used for the local shares on the computer, and then click OK.
    Note Type each host name on a separate line.
    Note If the BackConnectionHostNames registry entry exists as a REG_DWORD type, you have to delete the BackConnectionHostNames registry entry.
  7. Exit Registry Editor, and then restart the computer.
posted @ Tuesday, November 17, 2009 6:21 AM | Feedback (0)
Tongue in Cheek Geek Humor from the PDC

An old colleague (Biff Gaut) of mine has a great daily newsletter from the PDC.  This is certainly targeted for those of us looking for a “light” look at all things new that come out of PDC, but at times very technical with a perspective from someone who has been in the industry for some time (20+ years), started off as a C or C++ developer (not sure how early as I started with C/ASM).

But, as always, with the technical content comes the sometimes dry, humor that only Biff can interweave into the Geek content.

http://www.biffspdcnewsletter.com/2009/PDC2009Day1.aspx

To subscribe, find the email on his page it’s  “editor AT biffspdcnewsletter.com”

To go back a few years, take a look at some of his prescience`:

http://www.biffspdcnewsletter.com/default.aspx

Kind of reminds me of Mr. Bunny’s Guide to ActiveX – which is on my all time favorite reading list – if you know anything about ActiveX in the early days (COM to be specific), then this book is also a great, dry humor read.

Biff, I apologize for the overuse of the word “dry” in this post.

posted @ Tuesday, November 17, 2009 2:26 AM | Feedback (0)
Cleanup your Features…

Many times, your coding, etc. SharePoint features.  You’ll code something up, deploy, activate, etc. 

Using WSP builder, while a convenient tool, it also leaves some orphans around.  It forcibly deletes the solution leaving any place it’s activate with some “broken features”.

Fortunately, there’s a tool to help you cleanup those orphans.

http://featureadmin.codeplex.com/

posted @ Wednesday, November 11, 2009 8:34 AM | Feedback (0)
Minor update to the WSS Command Prompt…

 

Take the following and paste into a VBS file – then run.

Still need to choose the Link, then set the “Run as administrator” when UAC is on…

 

Set Shell = CreateObject("WScript.Shell") 
Set Env = Shell.Environment("PROCESS") 
DesktopPath = Shell.SpecialFolders("Desktop") 
Set link = Shell.CreateShortcut(DesktopPath & "\WSS CMD.lnk") 

cssHive = Env("CommonProgramFiles") & "\Microsoft Shared\web server extensions\12" 
currentPath = RTrim(Replace(WScript.ScriptFullName, WScript.ScriptName, "")) 
envBatFile = "setWssPath.cmd" 

CreateBatFile currentPath & setWssPath & envBatFile, cssHive 

link.Arguments = "/k " & " " & Chr(34) & currentPath & envBatFile & Chr(34) 
link.Description = "WSS Command Prompt" 
link.HotKey = "CTRL+SHIFT+W" 
link.IconLocation = "%SystemRoot%\system32\SHELL32.dll,94" 
link.TargetPath = "%comspec%" 
link.WindowStyle = 1 
link.WorkingDirectory = cssHive 
link.Save 
Sub CreateBatFile(fileName, cssHive) 
    Set fso = CreateObject("Scripting.FileSystemObject") 
    Set file = fso.CreateTextFile(fileName, True) 
    file.WriteLine("@SET PATH=%PATH%;" & cssHive & "\bin") 
    file.WriteLine("@ECHO WSS CMD Shell - Shawn Cicoria") 
    file.WriteLine("CD " & cssHive)

End Sub
posted @ Wednesday, November 11, 2009 7:59 AM | Feedback (0)
SharePoint 2010 Developer | Learn | Channel 9

Ted Pattison and Andrew Connell have a bunch of Learning SharePoint 2010 content up on Channel 9.

I can say, having attended Ted’s classes in the past, he’s one of the best to learn SharePoint development from.  He’s been at the forefront of getting to the reality of how to build things while working with the guidelines, rules, constraints of a “managed” platform such as SharePoint. 

If you get a chance take a look at these videos – even better, if you can attend in person, check out http://www.criticalpathtraining.com/ for classes.

SharePoint 2010 Developer | Learn | Channel 9

posted @ Wednesday, November 11, 2009 4:36 AM | Feedback (0)
TeamPrise acquired by Microsoft.

TeamPrise – the cross platform “client” for TFS, with Eclipse support (plug-in), command line – has been acquired by Microsoft.

So, we’ve been pushing folks to a 3rd parties to get back to the ALM Mothership – which is by far the best Enterprise class ALM platform that can scale from “1” person (see 2010 TFS) to thousands, geo-distributed – now, we can offer it direct resolving client’s concerns.

Not that the SourceGear guys are of concern, they’ve been around for quite some time.

This is great news.

http://www.microsoft.com/presspass/press/2009/nov09/11-09TeamprisePR.mspx

http://www.teamprise.com

http://www.microsoft.com/pathways/teamprise/

posted @ Monday, November 09, 2009 4:39 AM | Feedback (0)
Archives
Post Categories
Image Galleries
Other Blogs
News





Twitter


Tag Cloud