Visual Studio extensions for Windows SharePoint Services 1.1 CTP Release
Developers who are already building SharePoint solutions should check out the latest CTP. This has been posted on the SharePoint Designer Team blog.
You can get hold of the VSeWSS 1.1 CTP here.
The team has put a lot of thought into this build and has taken feedback from developers.
](https://www.chandima.net/Blog/Lists/Posts/Attachments/81/image_thumb_4.png) The main new feature for 1.1 is what we call “Solution Package editing”. In version 1 of VSeWSS, when you are building an application, the tool is implicitly creating a .WSP* file behind the scenes for you, which you can think of as a SharePoint “installer” file. When you hit F5/Debug, VSeWSS automatically installs this WSP solution package, as the mechanism for deploying the project files to the local SharePoint box. While this design has some nice benefits (e.g. VSeWSS doesn’t have to hard-code knowledge about where to install files on SharePoint), we heard loud and clear from SharePoint developers that they wanted more control over the WSP that was being automatically generated for them. That’s where the new “WSP View” comes into the picture. Using WSP View, you can now see the files and structure of the WSP Solution Package. You can also edit the WSP, changing what “Elements” live in what “Features”, as well as editing the (previously hidden) solution .xml files, e.g. Feature.xml. To bring up WSP View, go to the View menu and choose “Other Windows/WSP View”.*
If you don’t have the RTM version of the current release for VSeWSS you can download the release from the MS download site here.
I also found this great debugging article for SharePoint from Vince! Vince is the main man behind the CKS:EBE (Enhanced Blog Edition). He is also a member of the CKS team.