VSeWSS Version 1.0 has been released

VSeWSS - Visual Studio 2005 extensions for Windows SharePoint Services 3.0 version 1.0

Fri, 16 Mar 2007 12:15:35 GMT

PingBack from http://www.decatec.it/blogs/2007/03/16/VSeWSS+Visual+Studio+2005+Extensions+For+Windows+SharePoint+Services+30+Version+10.aspx

Link Listing - March 16, 2007

Christopher Steen — Sat, 17 Mar 2007 05:34:41 GMT

ClickOnce Community Resource Kit has found a new home [Via: brian@softinsight.com ] Health Monitoring...

SharePoint Developer Team Blog (who knew?)

Andrew Connell [MVP MOSS] — Mon, 19 Mar 2007 13:36:48 GMT

SharePoint Developer Team Blog (who knew?)

re: VSeWSS Version 1.0 has been released

erosen03 — Tue, 20 Mar 2007 21:00:07 GMT

This release does not install on an x64 development OS :(

VSeWSS Version 1.0

SharePoint, SharePoint and stuff — Thu, 22 Mar 2007 14:01:41 GMT

Microsoft hat die finale Version der Visual Studio 2005 Extensions for Windows SharePoint Services 3.0

re: VSeWSS Version 1.0 has been released

RAEdwards — Thu, 22 Mar 2007 23:33:26 GMT

Any chance this will be released to work on an XP box? I don't know about everyone else, but not all developers are working on a local Windows 2003 server when developing. I write code on an XP box and deploy to the server. I wanted to use the site def tools, but found out i couldn't install it. Oh well.

re: VSeWSS Version 1.0 has been released

Collutions — Wed, 28 Mar 2007 22:38:17 GMT

What a great tool!

How are localized solutions/resources/language packs handled?

I dug down into the manifest.xml file for the solution, added a <Resources> element and it was removed from the manifest.xml file upon deployment. Is localization something we need to do manually after the solutions is completed?

Any chance you could tell me whafiles power the deployment phase (targets, etc.) so that I can try to include resources/language packs in the solution?

Thanks again for a great tool!

What about X64?

avharris — Thu, 29 Mar 2007 00:32:33 GMT

Is there any hope of a 64-bit version being released? If not, are there any resoueces for creating web parts without the templates?

re: VSeWSS Version 1.0 has been released

spdev — Thu, 29 Mar 2007 13:40:26 GMT

Thank you for your comments, this is VSeWSS development team.

Q: Any chance this will be released to work on an XP box?

A: VSeWSS only runs on Windows Server 2003 with VS and WSS locally. Please see below topic for installation.

Preparing the development environment

http://blogs.msdn.com/spdev/archive/2007/01/26/preparing-the-development-environment.aspx

Q: How are localized solutions/resources/language packs handled?

A: WSeWSS removes all files under bin/<ship | debug>/solution before creating *.wsp file in deployment phase, the solution directory is just temporary directory for creating *.wsp file. That’s why your changes are gone after deployment.

If you would like to change contents of *.wsp file, you need to do follow steps.

1. Finish development on Visual Studio

2. Edit under bin/<ship | debug>/solution directory contents

3. Create *.wsp from the solution directory

4. Deploy & Activate the *.wsp via stsadm.exe

Q: Is there any hope of a 64-bit version being released?

A: Unfortunately we have no plan to release 64-bit version of VSeWSS.

Q: If not, are there any resoueces for creating web parts without the templates?

A: This article can help you.

Walkthrough: Creating a Basic Web Part

http://msdn2.microsoft.com/en-us/library/ms415817.aspx

re: VSeWSS Version 1.0 has been released

Donald D — Fri, 30 Mar 2007 18:58:13 GMT

I think tool is great, however I'm concerned about the licensing implications of needing to run everything in a VM. Is it not true that "technically" ( ie: legally, per MS licensing ) we need to have separately licensed copied of Server 2003, and VS 2005 for the VM ?

If so, then with all due respect, I feel your implementation is "less then ideal".

If not, then please advise.

Thanks.

re: VSeWSS Version 1.0 has been released

spdev — Fri, 13 Apr 2007 13:39:11 GMT

For your VM, you would need an additional license for Windows Server 2003, however you would not for Visual Studio since it is licensed per user. If you have a subscription to MSDN Universal, you get copies of everything for development and testing purposes.

Automating the construction and deployment of WSPs?

olidag — Thu, 24 May 2007 18:44:16 GMT

We have started using VSeWSS and so far it's pretty neat. The one thing we can't figure out is how to automate the solution creation and installation (i.e. like the "Deploy" action inside Visual Studio). This is for use on our continuous integration/build server.

We tried invoking msbuild with the "Publish" target, but it turns out that's only for Click-Once. There's no "Deploy" target, either and I can't find any additional .targets files that might have been installed as part of the add-in.

We also tried running devenv from the command-line with the "/Deploy Debug" option, but we get the following error:

"""

------ Deploy started: Project: AutomationTest, Configuration: Debug Any CPU ------

System.NotImplementedException

The method or operation is not implemented.

"""

...and adding the "/Log c:\vs.log" options just tells me the SPDevTools assembly was indeed loaded.

It looks like most of the magic takes place in SPDevTools.dll and, aside from trying to reverse engineer the public API in that assembly, we're lost.

Is there any way to automate the construction and deployment of the WSP file of Team Site Definition projects? We don't mind doing a bit of extra work, but we need an unattended mechanism, preferably in the form of an msbuild target...

Thanks!

- Oli

re: VSeWSS Version 1.0 has been released

serioja — Tue, 09 Sep 2008 22:14:31 GMT

Hi Oli,

I run into exactly the same problems with Visual Studio Extension 1.2 for VS2008. Does exists a solution to the problem you posted?

Serioja