Welcome to MSDN Blogs Sign in | Join | Help
VSeWSS Version 1.0 has been released

Greetings everyone, from Visual Studio 2005 extensions for Windows SharePoint Services 3.0 development team.

VSeWSS Version 1.0 has finally been released and is available for download on the web.
Please try our official version of VSeWSS and experience the Next-Generation SharePoint development. 

Visual Studio 2005 extensions for Windows SharePoint Services 3.0 version 1.0
http://www.microsoft.com/downloads/details.aspx?familyid=19f21e5e-b715-4f0c-b959-8c6dcbdc1057&displaylang=en

If you have the previous version (November CTP) of VSeWSS pre-installed on your PC, you must uninstall it before installing this version.
Please refer to the previous topic of this blog for the detailed instructions on installation steps.
The error regarding IE7 being found in the previous version has been fixed in this version.

We would like to express our sincere thanks to all of you who have been using and giving us valuable feedback on the Novemver CTP.
We hope that you continue to enjoy SharePoint development with VSeWSS.

Read the Japanese version of this article | 日本語版はこちら

Any opinions expressed in this blog are solely those of the author and not official positions of Microsoft Corporation.

Posted: Friday, March 16, 2007 6:12 PM by spdev

Comments

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

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

# March 16, 2007 5:15 AM

Christopher Steen said:

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

# March 16, 2007 10:34 PM

Andrew Connell [MVP MOSS] said:

SharePoint Developer Team Blog (who knew?)

# March 19, 2007 6:36 AM

erosen03 said:

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

# March 20, 2007 2:00 PM

SharePoint, SharePoint and stuff said:

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

# March 22, 2007 7:01 AM

RAEdwards said:

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.

# March 22, 2007 4:33 PM

Collutions said:

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!

# March 28, 2007 3:38 PM

avharris said:

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

# March 28, 2007 5:32 PM

spdev said:

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?

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?

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

# March 29, 2007 6:40 AM

Donald D said:

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.

# March 30, 2007 11:58 AM

spdev said:

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.  

# April 13, 2007 6:39 AM

olidag said:

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

# May 24, 2007 11:44 AM

serioja said:

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

# September 9, 2008 3:14 PM
Anonymous comments are disabled
Page view tracker