We have worked hard to listen and respond to the feedback from SharePoint Developers on VSeWSS. After VSeWSS 1.2 released in July 2008 we went out and talked to lots of SharePoint Developers about what they liked and didn't like about developing with VSeWSS. All of the new features in VSeWSS 1.3 are as a result of customer feedback, and there are lots of them. We just finished the VSeWSS 1.3 March 2009 CTP which released a couple of days ago. Read about the new features in the release notes and if there's anything we missed, please tell us.
If you want to see how easy it is to get going with SharePoint Development using VSeWSS, check out Kirk Evans short screecast showing building a Web Part, packaging and deploying it and some of the new features that make workarounds a thing of the past.
If you want to learn SharePoint Development using VSeWSS, check out the hands on labs and training videos at MSSharePointDeveloper.com.
Also released today is a set of 10 new theme projects for VSeWSS. These are individual Visual Studio 2008 projects which when deployed to SharePoint offer fresh new designed themes you can use in your projects.
VSeWSS will continue to be the recommended Microsoft tool for SharePoint Development until Visual Studio 2010 is released including a brand new set of SharePoint Tools. If you are a SharePoint Developer then your feedback about VSeWSS is important to us. You can give feedback on the tool at our Connect site here, or if you want to have a discussion about VSeWSS we recommend the MSDN SharePoint Development forum here. You can also give feedback as a comment on my blog and I will try to reply to anything posted here.
The Release To Web (RTW) of VSeWSS 1.3 is expected in July 2009 and we are not planning any further CTP releases.
If you want even more info about VSeWSS you can learn SharePoint Developer Best Practices direct from Microsoft Patterns and Practices published November 2008 here.
Paul, thanks for the update.
One thing Microsoft needs to keep in mind is that you tend to talk to SharePoint Developers. That's natural. But you may be missing a larger number of people who are not SharePoint developers because of the perceived difficulty of developing SharePoint solutions.
It would be unfortunate if you were missing perhaps twice the number of developers because, for instance, of weak support for developing on non-server systems. Existing SharePoint developers would not need that, or not much, but it may be preventing entry for others. You would never know that if you only talk to SharePoint developers.
E' stata appena rilasciata la versione di marzo delle Visual Studio Extension per SharePoint. (come
Novedades de Hoy: Ya esta disponible para descarga la versión RTM de Internet Explorer 8, así es, ya
Justo acabo de volver de ver Underworld 3 (están mejor las dos primeras partes) y me encuentro con qué
The final March 2009 CTP for the Visual Studio 2008 Extensions for SharePoint (v1.3) has now been recently
Hi Microsoft has released the last and final version of CTP for the Visual studio Extension for Visual
After installing the March 2009 CTP, I get the following error when I click Tools/Recycle App Pool :
Error recycling pool. Details: The system cannot find the path specified.
When I view External Tools, Recycle App Pool is defined as:
Title: Recycle App Pool
Command: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\bin\stsadm.exe
Arguments: -o recyclepool -pool mypool
When I look at IIS, Application Pools, SharePoint Central Administration v3, I see *TWO* entries for VSeWSS.
What can I do to fix this error?
John, thanks for the feedback. We have certainly heard this and it's high on the list for getting something done about.
Hi Fred, it seems like there is something amis with your installation either of the external tool (not part of VSeWSS) or with the VSeWSS install. I'd suggest you uninstall all of them and reinstall. VSeWSS has a recycle app pool command off the project right lick menu.
I (1)uninstalled, (2) manually renamed %programfiles%\Microsoft SharePoint Developer Tools 9.0\ to something else (because the CTP fails to completely uninstall itself - please fix this before final release), (3) reinstalled.
When I open up am existing SharePoint MOSS 2007 workflow solution and right-click on the project (not the solution), *I DO NOT SEE ANY RIGHT-CLICK MENU OPTIONS THAT SAY RECYCLE APP POOL*. When I click on the Tools menu and then select Recycle App Pool, I get the error message: Error recycling pool. Details: The system cannot find the path specified.
(1) why is the right-click menu option to recycle application pools missing? Is it because VSeWSS does not support Workflow solutions? That's a big disappointment if true because of all the things that need to have Application Pools Recycled, it's SharePoint (MOSS) workflows.
(2) What software is creating the Tools\Recycle App Pools\ menu option if it isn't VSeWSS 1.3 CTP Mar 2009?
No VSeWSS does not include SharePoint Workflow projects. These project templates are included in the Visual Studio 2008 main release. Because VSeWSS is being revised more often we have been able to add some things like apppool recycle which currently aren't in the SharePoint Workflow project template.
I would expect that something else on your machine is adding the Tools\Recycle App Pools menu option. It isn't standard Visual Studio or VSeWSS.
I installed VSeWSS 1.3 March 2009 CTP on my virtual machine. However I could not find a couple of templates in the sharepoint section when I tried creating a new project in VS 2008. They are:
1. Content Types
2. List definition from Content Type
I searched a lot on google but did not get a fix to this issue. Please help
If I attempt to create a new item using the WSP view after installing the 1.3 extenstions I get the following error any help please
2009/05/18 10:58:37 Error
System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ItemTemplatesCache\VisualBasic\SharePoint\1033\FeatureReceiver.zip\FeatureReceiver.vstemplate'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)
at System.Xml.XmlDownloadManager.GetStream(Uri uri, ICredentials credentials)
at System.Xml.XmlUrlResolver.GetEntity(Uri absoluteUri, String role, Type ofObjectToReturn)
at System.Xml.XmlTextReaderImpl.OpenUrlDelegate(Object xmlResolver)
at System.Threading.CompressedStack.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.CompressedStack.Run(CompressedStack compressedStack, ContextCallback callback, Object state)
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.Load(String filename)
at Microsoft.SharePoint.Tools.Wizards.NewFeatureWizard.SetWizardData(String templateFilePath, Dictionary`2 replacementsDictionary)
at Microsoft.SharePoint.Tools.Wizards.NewFeatureWizard.RunStarted(Object automationObject, Dictionary`2 replacementsDictionary, WizardRunKind runKind, Object customParams)
at Microsoft.SharePoint.Tools.Forms.SPToolWindow.CreateFeature(Object sender, EventArgs arguments)