I have been doing Visual Studion dotnet development for years. I have worked with Sharepoint since its inception in a few capacities but have not done any intensive development until now. We are about to unleash the beast within our organization
beginning with replacing our external web CMS with sharepoint. I performed a proof of concept and the results were great. Now that I have learned enough to be dangerous, I am wondering how developers out there are structuring their visual studio
solutions for sharepoint. The ability to have features is very powerful but if every piece of custom development we do ends up being a seperate feature, we are going to have web pages and list artifacts stored in a ton of different projects. I
am looking for how some other folks out there are managing their sharepoint develoment efforts.
What i have done so far is I have a core project that houses all of our custom pages so when we need to make changes to any pages they are located in one place. I feel this does not lend itself to the feature driven nature of Sharepoint development.
Then for lists and content types I have a project that is kind of a replacable project that gets cleaned after every deployment. So if I want to provision a new list declaritively I put it in this project similar to having a creat
View Complete Post