After a long hiatus...

After posting exclusively for the company I have worked for since 2006 (and still do) I am posting information on this blog again. Current projects:

SharePoint 2007 development
SharePoint 2010 development
SharePoint 2010 upgrade of corporate website
SQL 2008 R2 implementation,
Supporting a 2TB database
Silverlight development
Visual Studio 2008 and 2010 development

Windows Forms Development

After spending alot of time with ASP.NET, I was suprised to find how different Windows forms 2.0 is from the 2.0 version of ASP.NET. Take the ObjectDataSource control as an example.

I start by creating a class library containing a typed dataset containing a single simple SQLServer table. When I build it, and reference this in a new ASP.NET project, I can use the ObjectDataSource to find the right object, link to my DataSet1, and using the TableAdapter source displayed, select the getData() function. When I display default.aspx, the table data displays as expected.

Now for a Windows form. The ObjectDataSource control shows up as before, and I have both a DataTableBindingSource and a TableAdapterSource as candidates. The latter is useless, setting "ClearBeforeFill as a column name. The DataTableBindingSource sets up the correct columns, but when I display there is no data. Strange.

Content Management to use SharePoint

The next version of MCMS (WCM) will be built on top of SharePoint. This makes a ton of sense, but it was interesting hearing some of the issues that the Content Management team went through, and some of their tradeoffs. More to follow...

http://blogs.msdn.com/sharepoint/archive/2006/01/20/515564.aspx

SharePoint V3 Beta at Microsoft

The SharePoint development team has a blog, with some interesting information about their progress on V3.

http://blogs.msdn.com/sharepoint/archive/2006/01/20/515423.aspx

SharePoint 2003 with NET 2.0

Confirmed with Mike Fitzmaurice at Microsoft that SPS 2003 should work with NET 2.0 on the same box, and that SPS can index information stored in NET 2.0 web parts. Here is how:

- the IIS application running SPS must use NET 1.1 (ASP.NET tab)
- WSS SP2 is set up on a separate IIS application (virtual server) on the same machine, and configured to run NET 2.0
- Son of Smartpart is set up, and uses the WSS site
- Build webparts and controls in VS2005, and publish to WSS site

SPS should then be able to link to, and index the WSS site.

SharePoint Projects

Currently working on a project that integrates WSS 2.0 with NET 2.0, SPS 2003, SQL 2000 and SQL 2005, BizTalk 2004 and Content Management Server 2002. Wish me luck :-)