D'Arcy from Winnipeg
Solution Architecture, Business & Entrepreneurship, Microsoft, and Adoption

Fun with Sharepoint 2007 - Sharepoint != Source Safe

Monday, May 28, 2007 9:15 AM

So a co-worker of mine was talking with me about a project I'm working on right now that involves Sharepoint 2007. He was going to do a code review and I mentioned that my web part is in my solution, but the web page that was required by the web part was in Sharepoint. He said "Well, its a good idea to keep all files in source control."

POPPYCOCK I said...Sharepoint has a database, and besides: how annoying is it to maintain TWO different versions of the file: one that's accessed via the Sharepoint Designer and one that's through VS.NET? It was fine in Sharepoint alone...no need to clog up source control with a duplicate file.

So fast forward to today, when we're configuring a copy of our dev Sharepoint 2007 box so we can test deployment. Names on machines got changed, and now I can't access the dev box anymore (because it happened to get renamed...there were diff drives and such...like many romances on Facebook, its complicated). Long story short: I can't access my asp.net page now because Sharepoint Designer can't find the box and our IT guy is off on a call.

Lesson Learned: When dealing with files in Sharepoint that are ASP.NET, or anything development-sided for that manner, there needs to be a process in place to ensure that if the Sharepoint system goes bellyup, you have a backup available through regular source control means. I'm also curious to know if there's a way to have Sharepoint Designer check in/out files not only to Sharepoint but to another source control system as well, which would prevent these types of things from happening. ;)

I should have listened Jeremy, I should have listened...



# re: Fun with Sharepoint 2007 - Sharepoint != Source Safe

Do not forget that if you change stylesheets, xslt and other such things, you should also put them in your source control. 5/28/2007 11:06 AM | Ishai Sagi [MVP]

# re: Fun with Sharepoint 2007 - Sharepoint != Source Safe

Good tip Ishai, thanks. Do you know if there is a Microsoft best practice out there that you know of that bridges the gap between storing a version of a code-based document (i.e. asp.net page, stylesheet, xslt, etc.) in source control and also versioning it in Sharepoint2007?

I'm still trying to wrap my head around why I had to use the Sharepoint 2007 Designer to work in my asp.net page instead of just using Visual Studio...you'd think there would be a plugin of some sort that allowed VS.NET to interface with Sharepoint?

D 5/28/2007 11:17 AM | D'Arcy from Winnipeg

# re: Fun with Sharepoint 2007 - Sharepoint != Source Safe

I am disappointed that the Sharepoint Designer does not have Source Control integration. Since it has replaced Frontpage as a product and VS2005's HTML editor leaves alot to be desired, the new Sharepoint Designer 2007 is the obvious choice for editing HTML pages such as Release Notes etc. It has a brilliant UI and is excellent for working with CSS.

I stumbled across this article today. Thought it might be relevant (watch for wrap):-

1/10/2008 4:09 AM | Joe

# re: Fun with Sharepoint 2007 - Sharepoint != Source Safe

Did you find a solution to your problem? I've been trying to determine how to put Sharepoint files into a source control repository and can't seem to find any examples. We are using Subversion but anything at this stage that could provide some insight would be wonderful!/ 2/2/2010 9:13 AM | Jeannie

# re: Fun with Sharepoint 2007 - Sharepoint != Source Safe

Hi, i am planning to migrate my P drive documents into my current project Site. I would like to know how i can baseline my documents which are classed in folders and ensure easy traceability on SharePoint,including version control. 7/28/2011 10:51 PM | Raj

Post a comment