Any timelines as to release of VSeWSS 1.3 for VS 2008?
Hi,
We are waiting for VSeWSS 1.3 rtw -
Can you tell us something new about it ?
The release date supposes to be in the next few days.
10x alot,
Dan-Eyal Gazit
Development Manager
Hi Kris and Dan-Eyal,
The new release date I have is mid December 2009. Unfortunately this was delayed because the same team doing the release work are also working on SharePoint 2010 and there's a public beta coming up in November that they have been very busy with.
Regards,
Paul
Thanks for the information.
We are right in the middle of a large WCM project and VSeWSS 1.3 March CTP has been great, minus the few bugs here and there. VSeWSS really makes it easier for us SharePoint 2007 Devs, and having tools for the current platform is so important. It may be some time before we move to SP2010 so we need all we can get.
Can't wait to see the final release of VSeWSS 1.3.
Thank you for the nice information!
Real useful
Hey
Well mid December is only days ahead...
Do you have a final release date for us ?
10x
Hi Dan-Eyal,
Unfortunately the release has slipped. Please continue to use the March CTP and report any issues you find at http://MSSharePointForums.com
Sorry to hear that VSeWSS 1.3 final release won't happen in December 2009.
I hope the SharePoint 2010 team that is also responsible for finishing VSeWSS 1.3 realize that failure to provide the final version of VSeWSS 1.3 will start to become an impediment to upgrades from SharePoint 2007 to 2010 very soon. That in turn means it will impact Microsoft's bottom line MORE than the cost of finishing VSeWSS 1.3.
I know it's more fun to work on the bright, new, shiny Visual Studio 2010 templates for SharePoint development, but for Christ's sake, we were told at the May 2009 Regional SharePoint Conference in Virginia that the final version of VSeWSS 1.3 would be out "sometime this Summer". Throw in the fact that at that same conference, we were told that the only *SUPPORTED" upgrade path for our custom C# SharePoint code would be via solutions generated via VSeWSS; therefore, if we weren't using it to generate our WSP's, we darn well better start using it right away or we would be left to our own devices for converting to SharePoint 2010 + Visual Studio 2010.
