XPe and SourceSafe/SVN

  • Thread starter Thread starter David Berman
  • Start date Start date
D

David Berman

I am trying to backup my xpe configurations and whole database into my
source code control system. But am unsure the best way to do this and don't
want to miss anything. I also want to make sure I can check out and check
in the slx and database.

Has anyone done this and if so can you email me a word/html doc if you have
one on what I should do?

Thanks,
David
spam123 aaht qiot dot comm
 
I am trying to backup my xpe configurations and whole database into my
source code control system
Click to expand...

My attempts at backup have all failed. :-) I have merely tried to do a
backup using ZIP files stored on an external hard drive.

I have decided that instead, I will shift all XPe work to virtual machines.
These are then self-contained working XPe "platform builder" appliances.


Warren
 
Thanks for your comments on that it didn't work for you.

But does anyone have a successful experience to share with SourceSafe/SVN
and XPe?

Thanks
 
Hi David,

I guess it's not very feasible with SVN:

1. The size of the .sld file is quite big (in my case whole solution is
~70Mb) and it's UNICODE. I'm not 100% sure, but AFAIK SVN will consider
UNICODE file as binary and can't provide decent storage / comparison
functions. Then, even if it's a plain text file, the internal format of
the file is cumbersome and visualizing 3 pages of changes if one
component was added / removed - will not help much.

2. The components also are not very suitable, as they need repository
files - SVN database will grow rapidly with each commit.


Microsoft should invent something useful for the XPe in this area...

Nikolai
 
We've used SourceSafe with no problems.

We save the project file and the log file in SourceSafe.

Get them when you want to do anything to the image then re-build.

Save both files back to SourceSafe.

The SLX file is binary so SourceSafe will just tell you the versions are
different BUT the log file is text so you can use that to spot changes in the
components that are installed. (But not any changes to settings on any
components).

There is a GOTCHA (isn't there always). the log file is Unicode text so
you'll need VSS 2005 or later. We had VSS 6.0 which just treated the log
file as a binary file.

hope this is helpful

Kevin
 
Back
Top