I used VseWSS VS 2008 extensions for a custom workflow project and loved it,, the way it allowed me to choose the list when creating the project and other options .. meant I can concentrate on core logic without worrying about anything.
Okay now crucial part -- how to do deployment .. I created 12 hive folder structure in the project ,,, and copied feature and workflow file to it.. used WSPBuilder VS add-in and got my wsp created for deployment. On Wed, Feb 25, 2009 at 2:25 AM, Clayton James <[email protected]>wrote: > > > Hi Jeremy > > > > Most files that are deployed via Solutions are deployed to folders located > under the TEMPLATE directory. The current version (VSeWSS 1.2) allows you to > easily deploy files to this location by adding a project item called > ‘Template’. This adds a folder to your VS project called Templates (see > image below) and anything located underneath this folder is deployed to the > same location on the WFE starting at the TEMPLATE directory. How easy is > that. > > > > > > So using VSeWSS we can follow the 12 hive structure but we are beginning at > the Template directory and not the 12 directory. > > There is a limitation with the current version (VSeWSS 1.2) that it is > difficult to deploy files to the 12 directory and its sub directories > (excluding the Template directory). The Template directory sits below the 12 > directory so adding the Templates project item won’t help. However, the new > version of VSeWSS 1.3 has a new project item called RootFiles which sounds > like it might address this issue. > > > > There are also some much needed additions and fixes in the new version. > > > > The new 1.3 version has some much needed features. > > · Separate build commands for deploy and retract > > · Ancillary assemblies such as for business logic can now be added > to the SharePoint Solution WSP – this was always painful. You would have to > manually copy your business assemblies into your web part project before you > packaged it up as a .wsp > > · Refactoring Support: This was a major pain if you wanted to > change your Web Part name > > · Solution Generator and generate solutions from publishing sites > > · Bug Fixes in wsp view > > > > HTH > > > > Clayton > > > > > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Jeremy > Thake > *Sent:* Tuesday, 24 February 2009 5:24 PM > *To:* [email protected] > *Subject:* RE: Why not VSeWSS ? > > > > Ishai, I’d like to pick up on your point about VSeWSS and why you don’t > recommend it. > > > > The main negative point I hear from the community is around the fact it > doesn’t follow the 12 hive structure. > > This wiki page documents the community discussions so far: > > > http://www.sharepointdevwiki.com/display/public/Solution+package+development+tool+comparisons > > > > Be great to get your feedback on this stuff. I’m assuming you’re a > WSPBuilder fan? > > > > With your experience, are there things you’d like to see in ‘the Ultimate > SharePoint Development Tool’? > > > http://www.sharepointdevwiki.com/display/public/The+Ultimate+SharePoint+Development+Tool > > > > > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Ishai > Sagi > *Sent:* Tuesday, February 24, 2009 3:02 PM > *To:* [email protected] > *Subject:* RE: Feb 2009 CTP of Visual Studio 2008 extensions for Windows > SharePoint Services 3.0 has been released! > > > > Bill, > > Setting aside the VseWSS discussion – which you know I am with you on those > points and others, and I do not use that product, and I recommend against it > to my clients (that was a long “set aside” sentence) – I do not agree about > windows XP as what you should be working on. > > > > I don’t think a development environment described in the first point you > made is as hard to achieve as you make it to be. > > > > What organisations should do (and do) is get a virtualised *environment *with > a *physical* SQL cluster and domain controller for the development > environment. Each developer gets a virtualised server to develop on with > MOSS or WSS installed (depending on licences). Sysprep is not that easy in > this scenario – because you still need to rename the machine, and create new > databases in SQL. Performance should be good for development (if the VM > machine is big enough). > > > > However, if you want to avoid scripting this (and we know that can be > done), an easy way to solve this is to install MOSS – but then disconnect it > from the farm before making the image. Then, when a new machine gets > provisioned, the developer only has to run the configuration mechanism to > connect it to the SQL cluster and create the databases. You save a lot of > time in installing – just running a wizard after the provisioning has taken > place. You can even maintain your image with service packs – install them on > the image, and do not connect it to any farm... > > > > > > *Ishai Sagi* > Solutions Architect > *Information Services* > > * > *Mobile: 04 2379 1728 > Email: [email protected] > Web: www.uniqueworld.net > Blog: www.sharepoint-tips.com > [image: cid:[email protected]] <http://www.uniqueworld.net/> > > > ------------------------------ > > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > > Subscribe: [email protected] > > Unsubscribe: [email protected] > > List FAQ: > ------------------------------ > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/ozmoss > Other lists you might want to join: http://www.codify.com/lists > lang=EN-US>http://www.codify.com/lists/ozmoss > > Other lists you might want to join: http://www.codify.com/lists > > e='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'> > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Bill > Williamson > *Sent:* Tuesday, 24 February 2009 4:45 PM > *To:* [email protected] > *Subject:* Re: Feb 2009 CTP of Visual Studio 2008 extensions for Windows > SharePoint Services 3.0 has been released! > > > > Point: Why do they give you ASP.NET <http://asp.net/> in visual studio on > XP when ASP.NET <http://asp.net/> is a server application? > > From a VERY basic functionality standpoint you cannot EVER open a project > from codeplex/etc if it's created using these tools unless you are running a > server OS. How is that reasonable? The very minimum they should be doing is > providing the project templates as a standalone component... > > On top of that, though, it should support remote deploy and debugging. It > is just plain lazy of MS to not do so. > > IDEALY there should be a localhost version of WSS that you can use in XP > for debugging. Then you deploy to your development integration environment. > Then you deploy to test... etc. > > > As it is now you have two options: > 1. Each and every developer has their own sharepoint instance. For most > organizations that means a VM, as you are forced into a SOE for your > desktop. This means a server install, an SQL install, a MOSS install, etc. > For each developer, since templating it is not support currently. > > 2. You share a dev server and pray no one else is debugging when you need > to... > > I'm not sure which is worse, but they're both horrible. > > THere is NOTHING "magical" about windows server vs windows client > (xp/vista). Both have most of the same DLLs. Vista even has IIS 7. The ONLY > reason it does not run on XP/Vista is because MS do a check so that they can > make you pay more for licensing. It would run (and people have made it do > so) easily. A "localhost only" version (JUST like casini asp.net server > built into VStudio!) should be built. > > On Tue, Feb 24, 2009 at 4:22 PM, Daniel Brown <[email protected]> > wrote: > > Why would you install these on XP when WSS/MOSS is a server application? > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Bill > Williamson > *Sent:* Tuesday, 24 February 2009 3:46 PM > > > *To:* [email protected] > *Subject:* Re: Feb 2009 CTP of Visual Studio 2008 extensions for Windows > SharePoint Services 3.0 has been released! > > Please tell me you can install it on Xp.... > > On Tue, Feb 24, 2009 at 4:05 PM, Aaron Saikovski < > [email protected]> wrote: > > Not sure if you guys have heard but we have updated and released the Feb > 2009 CTP of the VS2008 extensions for WSSV3.0. > > More details can be found here: > > > http://www.microsoftcom/downloads/details.aspx?FamilyID=b2c0b628-5cab-48c1-8cae-c34c1ccbdc0a&DisplayLang=en<http://www.microsoft.com/downloads/details.aspx?FamilyID=b2c0b628-5cab-48c1-8cae-c34c1ccbdc0a&DisplayLang=en> > > enjoy. > > Regards, > > Aaron > ------------------------------ > > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > > Subscribe: [email protected] > > Unsubscribe: [email protected] > > List FAQ: http://www.codify.com/lists/ozmoss > > Other lists you might want to join: http://www.codify.com/lists > ------------------------------ > > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > > Subscribe: [email protected] > > Unsubscribe: [email protected] > > List FAQ: http://www.codify.com/lists/ozmoss > > Other lists you might want to join: http://www.codify.com/lists > ------------------------------ > > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > > Subscribe: [email protected] > > Unsubscribe: [email protected] > > List FAQ: http://www.codify.com/lists/ozmoss > > Other lists you might want to join: http://www.codify.com/lists > > > ------------------------------ > > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > > Subscribe: [email protected] > > Unsubscribe: [email protected] > > List FAQ: http://www.codify.com/lists/ozmoss > > Other lists you might want to join: http://www.codify.com/lists > ------------------------------ > > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > > Subscribe: [email protected] > > Unsubscribe: [email protected] > > List FAQ: http://www.codify.com/lists/ozmoss > > Other lists you might want to join: http://www.codify.com/lists > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.0.237 / Virus Database: 270.11.3/1969 - Release Date: 02/24/09 > 06:43:00 > -------------------------------------------------------------------------------- Support procedure: http://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists
<<image001.gif>>
<<image002.png>>
