Best project format for deploying VS2005 + SharePoint?

Question

First, let me use one sentence to release some disappointment: "My god developing for SharePoint is a mess."

OK, sorry, let me focus on 1 specific scenario. I developed (VS2005) some functionality that works if I use it as a DLL on a SharePoint server (MOSS2007). Now I'm trying to determine the best way to package it as a deployable function.

Based on the search results, you would think that no one ever did this in duplicate! Each article contradicts the following or documents a technique that addresses some issues with other methods and, in turn, is likely to be updated in another article. Many of them seem to be based on inherited methods for 2003, WSS, etc. Some recommend using MSBuild tasks for deployment in your code, manually copying files to directories with names like "12" or using tools such as SharePoint Designer, or making changes directly to the server. This sounds like hacks that developers will use to install on test server. Has anyone ever created a project that, after a successful build, can be transferred to another machine and deployed using the installer or command line command through STSADM?

I admit that I am only new to SharePoint administration, but this should be simpler than it seems. I think I understand the basic concepts at http://msdn.microsoft.com/en-us/library/ms413687.aspx , but there is no way to automate this? There should be one recommended practice for packaging features that will be deployed on a 2007 server. But for life, I can’t understand what it is. (My best guess is that it is something like this: http://www.codeplex.com/sptemplateland , but this has not been updated since February 2007.)

Can anyone help? Thank you very much!

Answer 1

“Street conversation” is usually associated with three options for the development of SharePoint.

• VSeWSS, Microsoft's own extensions for Visual Studio .
• STSDEV pre-creates the VS solution based on your specifications
• WSPBuilder , my preferences due to integration with it

Everyone has strengths and weaknesses, and I advise you to try all three to find your preference.

.b

Answer 2

Using VSeWSS 1.2, I would recommend creating an STSDEV solution that completes the code and copies the website to the right place.

Update However, VSeWSS 1.3 is now the “official” MS, and it will be supported in future versions of Visual Studio, so this will probably be the route.

Unfortunately, you still need to know where each thing must meet the requirements of SharePoint in order to make it work. Under the hood, the solution and function still use gnarly XML formats to control the direction of all bits of the solution.

After a while, the sharp pain you feel dulls to a low ripple.