SmartTemplates is actually built on top of WSPBuilder. So you can plug into all of the WSPBuilder features.
WSP builder handles the creation of a MOSS wsp file. SmartTemplates gives you VS.net project templates that make use of WSPBuilder. On Feb 11, 2008 3:40 PM, Ishai Sagi <[EMAIL PROTECTED]> wrote: > Check out WSPBiulder on codeplex. good platform for features and web parts > and the like, with support for VS2008 in the latest release. > http://www.codeplex.com/wspbuilder > > Unlike smarttemplates it has more than just a template for web parts... > > ________________________________________ > From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Simon Cropp [EMAIL > PROTECTED] > Sent: Monday, 11 February 2008 3:35 PM > To: [email protected] > Subject: Re: [OzMOSS] Source control with MOSS 2007 > > > Ok > > You really need to separate this question out into two. > > 1. What version of Visual Studio (2205 or 2008) should we use > for MOSS development? > 2. What source control system should we use for MOSS development? > > Answers > > 1. Unfortunately there is no template support from MS (At the > moment) for MOSS in Visual Studio 2008. The current "WSS extensions > for Visual Studio 2005", as they state, are specifically for Visual > Studio 2005. > http://www.microsoft.com/downloads/details.aspx?FamilyId=19F21E5E-B715-4F0C-B959-8C6DCBDC1057&displaylang=en > http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2473445&SiteID=1 > I understand that MS is looking into this at the moment. > This means it is a little harder to create webparts and deployment > projects for MOSS when using 2008. But not impossible. There are also > a number of tools that are currently filling this gap. One, I am > using, is SmartTemplates (http://www.codeplex.com/smarttemplates). It > works seamlessly for simple scenarios. It is also fairly easy to > extend for more advance scenarios. So I would say "Yes" move over to > 2008. The new feature provided outweigh the minor problems you may > have integrating it with MOSS. > > 2. This is really not a question about MOSS. Source control is a > decision an organization should make across the board. It is not > affected by what technology your projects are based on. > My recommendation (based on the source control systems I have used). > > VSS > Don't use VSS. It is old clunky and a simply pain in the butt. > > TFS > TFS is good. Still has a few wrinkles to iron out but for a large > enterprise it is a good fit. Features like workitems, bug tracking, > integration with MS Project and MS outlook, and many free addins > available make it a great tool. > > SVN > Source control and nothing else. It can integrate with both VS 2005 > and VS 2008 or be controlled externally of the dev environment. Great > at what it does but has none of the advanced features of TFS. It has > no work items, no office integration, no bug tracking. So this is > better for smaller teams. > > The other option – TFS with SVNBridge > MS has recently release a new project called SVNBridge > (http://www.codeplex.com/SvnBridge). This allows you to use SVN tools > like TortoiseSVN and VisualSVN to talk to TFS. What this means is that > instead of using the Source control binding built into VisualStudio > you use SVN style integration. This gets rid of many of the bugs and > problems that people have with the Visual Studio bindings. I would > recommend this option. Note: you can still use all of the advanced > features of TFS though VS.net > > I will leave it to other people to comment on other source control systems. > > > > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the list > with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > > > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the list > with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > > > ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net
