So with the message from Paul Andrew on the Sneak Peek webcast to start using VSeWSS now so that you will be familiar with Visual Studio 2010 tools, I started to take a look at VSeWSS 1.3 CTP (March not Feb). It is truly painful to work with compared to WSPBuilder and STSDev. The community has been maintaining this page on the comparison between the tools and I’ve been adding a few extra bits today on simple things like creating features and feature receivers using it.

Don’t write off 2007 guys

I suspect with VS2010 supporting SharePoint 2010 we may have to wait for that to be released. If Visual Studio 2010 is anything like SharePoint Designer 2010 with it not being backward compatible with SharePoint 2007, then we will still require stronger tools for 2007.

One other thing I'd like to point out is that there are still SharePoint 2003 servers around, and there will be SharePoint 2007 servers around for a long time before they move up to SharePoint 2010! Mainly because the developer toolset has never been that great and people have hacked and slashed at servers and at Web UI customisations instead. This has lead to fear in updating to a service pack…let alone a full release to SharePoint 2010!

Thank you Community

All I can say is thank you to the awesome SharePoint community…and especially thanks to Carsten Keutmann for WSPBuilder! And the surveys don’t lie in terms of the percentage of people using WSPBuilder (55%) over VSeWSS (10%).

Voice your concerns!

The question has been posed on the forum…please add your support to this!