Using VSS with Target Designer

[Guest]

I'm now getting to the stage of releasing my buold of Embedded XP onto our
equipment.

I'd like to be able to use the control facilities of VSS to lock down my
image configuration file so that i can keep a change history.

there are two problems with this.

1. the configuration file is binary so VSS simply reports that the files
are either the same or different.
2. i'm not sure what target designer will do if i try and open a read-only
configuration file. (i must admit i'm quite nervous about doing that so i
thought i'd ask the question first)

Whats the best was of controlling different releases of an XPe image?

 

[KM]

Kevin,

Unfortunately, there is no XPe Tools integration with VSS, nor with any other source control engine :-(. (would love to see it's
working with VS Team SC server)

Anyway, just to answer you questions:
1) How about saving SLX as XML?
Hope you use FP2007 where the feature works much stable than in previous versions of the toolkit.

2) You don't need to open read-only files (obviously, TD won't be able to save to read only file). You can always check-out or
make it writable the file in VSS before you open it up with TD.

 

[Sean Liming \(eMVP\)]

Someone used my SLDXAssistant tool and the SLDDIFF.EXE
(http://www.seanliming.com/Tools.html) to save difference between changes of
SLX and SLD files to version control.

Regards,

Sean Liming
www.sjjmicro.com / www.seanliming.com
XP Embedded Book Author - XP Embedded Advanced, XP Embedded Supplemental
Toolkit

 

[Guest]

Sean and KM

Thanks for the input. I'll look at the tools tomorrow.

I figure i could do a diff on the build log files so i can keep track of
what changes between versions.

 

[KM]

Kevin,

For tracking purposes you can definitely use build logs.
Also, in the ConfigurationExplorer component of XPeTools package (www.xpefiles.com) I exposed a function to save SLX as a plan text
file - list of components included in to the configuration.