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...
D