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: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Ishai Sagi Sent: Tuesday, February 24, 2009 3:02 PM To: ozmoss@ozmoss.com 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: ishai.s...@uniqueworld.net<mailto:ishai.s...@uniqueworld.net> Web: www.uniqueworld.net<http://www.uniqueworld.net> Blog: www.sharepoint-tips.com<http://www.sharepoint-tips.com/> [cid:image001.gif@01C9969C.47BE2CC0]<http://www.uniqueworld.net/> From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Bill Williamson Sent: Tuesday, 24 February 2009 4:45 PM To: ozmoss@ozmoss.com 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<http://asp.net> server built into VStudio!) should be built. On Tue, Feb 24, 2009 at 4:22 PM, Daniel Brown <dani...@hostworks.com.au<mailto:dani...@hostworks.com.au>> wrote: Why would you install these on XP when WSS/MOSS is a server application? From: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> [mailto:ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>] On Behalf Of Bill Williamson Sent: Tuesday, 24 February 2009 3:46 PM To: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> 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 <aaron.saikov...@microsoft.com<mailto:aaron.saikov...@microsoft.com>> 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: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> Subscribe: ozmoss-subscr...@ozmoss.com<mailto:ozmoss-subscr...@ozmoss.com> Unsubscribe: ozmoss-unsubscr...@ozmoss.com<mailto:ozmoss-unsubscr...@ozmoss.com> 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: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> Subscribe: ozmoss-subscr...@ozmoss.com<mailto:ozmoss-subscr...@ozmoss.com> Unsubscribe: ozmoss-unsubscr...@ozmoss.com<mailto:ozmoss-unsubscr...@ozmoss.com> 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: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> Subscribe: ozmoss-subscr...@ozmoss.com<mailto:ozmoss-subscr...@ozmoss.com> Unsubscribe: ozmoss-unsubscr...@ozmoss.com<mailto:ozmoss-unsubscr...@ozmoss.com> 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: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com 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: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists -------------------------------------------------------------------------------- Support procedure: http://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists
<<inline: image001.gif>>
