Geeks With Blogs

Tangible Thoughts SharePoint, MOSS? and all the other questions

I've been pondering about the lack of a more efficent process for developing  MOSS/WSS Solutions (I mean a solution to a business probelm and not a wsp) lately, because believe it or not, when your MOSS Solution contains more than just one component, e.g. WebParts, Features, ASPX pages, Workflows etc, there is no Solution template in Visual Studio where you can add all these project types and have them compile to a single wsp. Its kind of a pain to develop without this functionality.

Serge pointed me out to WSPBuilder by Carsten the other day (man was I so out of it :( ). But wait Rich Finn has done a number on the WSPBuilder and introduced it as a Visual Studio Template. Which should be a help, but doesnt really solve the problem of multiple projects.

So here is whats spinning around in my head. A Visual Studio Project type (Setup and Deployment or any other kind) which you can add to your Solution, and to which you will add references from your other projects. The project would be intelligent enough to determine the output type of the referred projects and place the output in the appropriate folder structure as per WSPBuilder, and on compile time call wsp builder.

I think its an interesting idea that would ease a bit of pain from the developent chores involved with MOSS Solutions, but implementing it might be a bit of a challenge.

Does anyone else have any other ideas? or recommendations/tips on this or  how they go about developing MOSS/WSS Solutions.

 

Cross-posted from tariqayad.com

Posted on Saturday, September 29, 2007 2:48 AM SharePoint | Back to top


Comments on this post: VS Template for WSPBuilder?

# re: VS Template for WSPBuilder?
Requesting Gravatar...
Hi there,
Another way to do it: the "SharePoint Solution Builder"
http://www.gavd.net/servers/sharepointv3/spsv3_item.aspx?top=5&itm=431
Left by Arthur on Nov 06, 2007 9:28 AM

# re: VS Template for WSPBuilder?
Requesting Gravatar...
I use WSPBuilder (with a few of my own extensions), and where more than one assembly is needed, I find that dragging from the bin folder to the gac folder of the WSPBuilder project works reasonably well. It's not ideal and I'm thinking about automating it, but with the right project structure it doesn't matter that much.

With WSPBuilder the solution package is a project and the features, web parts, pages etc are items. Stay away from the VSeWSS templates if you want to maintain a reasonable structure for your projects.
Left by Tom Clarkson on Nov 29, 2007 9:47 PM

# re: VS Template for WSPBuilder?
Requesting Gravatar...
Thanks .. !
Left by mp3 on Dec 19, 2007 9:34 PM

# re: VS Template for WSPBuilder?
Requesting Gravatar...
You have very interesting site.Thanks for all.
Left by bilard on Jan 11, 2008 11:02 AM

# re: VS Template for WSPBuilder?
Requesting Gravatar...
Thanks for Work, good achievement
Left by diziler on Jan 17, 2008 8:38 AM

# re: VS Template for WSPBuilder?
Requesting Gravatar...
thanks for work webmasterdestek
Left by webmasterdestek on Feb 02, 2008 9:25 AM

# re: VS Template for WSPBuilder?
Requesting Gravatar...
Thanks for Work, good achievement
Left by oyun indir on Feb 07, 2008 3:03 AM

# re: VS Template for WSPBuilder?
Requesting Gravatar...
thank you comment
Left by hikaye on Feb 24, 2008 4:46 AM

Comments have been closed on this topic.
Copyright © Tariq | Powered by: GeeksWithBlogs.net