Comments on: VSeWSS v1.3 and source control http://allowunsafeupdates.com/2009/05/31/vsewss-v1-3-and-source-control/ Something to say about most things Thu, 03 Nov 2011 05:22:06 +0000 hourly 1 http://wordpress.com/ By: Matt http://allowunsafeupdates.com/2009/05/31/vsewss-v1-3-and-source-control/#comment-28 Sat, 13 Jun 2009 19:34:53 +0000 http://allowunsafeupdates.wordpress.com/?p=73#comment-28 Thanks for the clarification Paul and that’s great to know about the supported upgrade path to VS2010!

]]> By: Paul Andrew http://allowunsafeupdates.com/2009/05/31/vsewss-v1-3-and-source-control/#comment-27 Sat, 13 Jun 2009 15:46:40 +0000 http://allowunsafeupdates.wordpress.com/?p=73#comment-27 Hi, I wanted to help you with your problem with VSeWSS. You said “because the feature.xml files are dynamically generated” but they really aren’t. The trick is that there are two sets of configuration files for building WSP SharePoint Solutions. One is in .\PKG and these files are only generated if they don’t already exist. They are also edited by the WSP View and you can edit these files. We have detailed instructions for editing them in the VSeWSS 1.3 Release Notes. The other set are .\bin\Debug\PKG and these are generated at the time of build.

You also asked about upgrade to Visual Studio 2010 SharePoint tools. Once SharePoint 2010 is publicly available we will have an upgrade tool to take VSeWSS projects and upgrade them to Visual Studio 2010 SharePoint tools. We will support VSeWSS 1.1, 1.2 and 1.3 with this tool, but not 1.0.

Hope this helps.

Regards,
Paul

]]>