point-n-click

I really love when a fix is simple. Back story : in this case, I am in the midst of using a combination of wspbuilder and spsource to reverse engineer, package up and deploy a few custom content types. wspbuilder is a codeplex Visual Studio extension that helps package up SharePoint code into a Solution file (WSP) for deployment. spsource is another tool that tries to analyse a SharePoint site and tease out a schema.xml for a list, and column & field information for a content type.  I use the term 'tries' because depending on how clean your dev environment is, your mileage may vary.  Problem description : when running WSPBuilder -> Build WSP, the output window in Visual Studio says Could not load file or assembly 'CabLib, Version=6.9.26.0, Culture=neutral, PublicKeyToken=85376ef9a48d191a' or one of its dependencies. An attempt was made to load a program with an incorrect format. It is my belief this problem is related to the installer not detecting/s...

The visual studio 2008 command here powertoy, redux for windows 2008 32 bit, installation of visual studio on the c: drive. I know that someone will want this exact thing rather than pecking through the INF file themselves. Download Install Here . Right click on the INF file and select Install. ref: Scott Hanselman and http://accidentaltechnologist.com/programming/visual-studio-2008-command-prompt-here-on-vista-64/ p.s. the uninstall is botched; it leaves its registry folders in place for some reason. If someone fixes this, great, in the mean time just don't uninstall it

Following Robert Shelton's well documented series on creating MOSS 2007 workflows in Visual Studio 2008, I ran across a bit of a snafu. Basically, his recommended dev machine setup stipulates WSS3, VS2008, etc. However the Visual Studio 2008 wizards/templates for Sequential Workflow expect MOSS, not WSS. The workaround should get me positioned to develop, debug, package and deploy workflows in VS2008. I found the most complete workaround write-up on this issue on the Visual Studio SharePoint Tools Blog by Roger Best. Here is his writeup in full (in case the link stops working one day..) "Getting Visual Studio 2008 SharePoint 2007 Sequential / State Machine Workflow projects working with Windows SharePoint Services 3.0 Published 19 August 08 02:18 PM I wanted to create a SharePoint workflow using VS 2008 on WSS 3.0. The documentation is set that only Microsoft Office SharePoint Server 2007 can be used but I figured I would lay out the modifications needed to allow a pro...

After arm wrestling the 64 bit version of MOSS 2007 + Windows 2008 x64 + Visual Studio 2008 x64 (and Visual Studio 2010 Beta 1 x64) , and LOSING - I was cornered into SharePoint Designer for development of workflows. Now, I know the inefficiency I'm invoking by doing this - instance creation versus template creation! But deadlines beg, you know. So how pleased am I that when I eventually get my x86 (ow, what year is it? I think I've been writing for x86 platforms for something like 20+years, yikes) VM dev instance in HyperV up and running, I'll be able to reuse/import the SPD built workflow logic into Visual Studio. Warning, there is excessive winking in this blog entry: http://blogs.msdn.com/sharepointdesigner/archive/2007/07/06/porting-sharepoint-designer-workflows-to-visual-studio.aspx The other nugget of the day is that I think I'll write up my findings of first release of Google Chrome for Mac OSX and the SharePoint experience. Chrome is built on webkit rendering,...

This is Yet Another Blog on how to properly install & configure a SharePoint 2007 development client installation. I've read many different blogs and noticed pretty substantial inconsistencies and invariably most come to the conclusion that Your Mileage May Vary. Case and point, in my dev environment, I'm optimized for the current bleeding edge, and there is a whole lot of blood. Dev setup: OSes Windows 2008 Server 64 bit for the Dev Server One configuration that didn't work for the Dev Client - Windows 7 RC1 (Build 7100) 64 bit (HP Compaq workstation, 2gb ram); the reason that I need to have a client/server is due to a limitation of Visual Studio 2008 and VS 2010 Beta 1's SharePoint Workflow Project creation running on a 64 bit OS - http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=325668 Dev Client - Windows XP SP3, dual core E2220 CPU at 2.4 GHz, 2GB RAM Configuration to be continued...

After installing VS2008 pro on the sharepoint 2007 64 bit win2k8 server, I create a new SharePoint Sequential Workflow project and get the dreaded "Object reference not set to an instance of an object" dialog. A similar project creation failure occurs using Visual Studio 2010 Beta 1 on the 64 bit MOSS 2007 server too. In the case of the newer IDE however, there is no dialog box, rather the status bar on the bottom says Creating project 'SharePointWorkflow1'... project creation failed. So it seems like the "plan" as indicated by the Program Manager is currently half implemented. The VS2010 Beta 1 actually shows these project templates to the user on a 64 bit environment (not according to plan), however the project creation fails (seemingly by design). >"The plan for Visual Studio 2010 is to still not support SharePoint 2007 Workflow projects on a 64bit workstation. VS 2010 will avoid the problem of throwing exceptions by hiding the Project Templates ...