Save project as XML by default?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I want to be able to compare difference between projects as part of our source control system (using Beyond Compare). This works well if I save the project as XML, as it's quite easy see what's changed.

However, it's a right royal pain in the butt when XPe Target Designer overwrites the file with a non-XML version. It seems to have to do a SaveAs to get it to save as a XML (with the same file extension -which is weird).

Any way of changing TD's default file format?
 
Mark Gillespie said:
I want to be able to compare difference between projects as part of our source control system (using Beyond Compare). This works well if I save the project as XML, as it's quite easy see what's changed.

However, it's a right royal pain in the butt when XPe Target Designer overwrites the file with a non-XML version. It seems to have to do a SaveAs to get it to save as a XML (with the same file extension -which is weird).

Any way of changing TD's default file format?
Click to expand...


Having now seen what using this file format does to my project file, I no longer want to save as XML ... :-(

I think I'll stick to the default binary format....
 
Mark,

In case you still need a text based format of the configuration to do the
comparision.
You may take a look at the XPeTools component package/Configuration Explorer
component from www.xpefiles.com (Development Utilities/Main folder). This
component will allow you to save your Configuration as a plain text list of
the components included. Then you can do the comparision pretty easy.

KM

source control system (using Beyond Compare). This works well if I save the
project as XML, as it's quite easy see what's changed.overwrites the file with a non-XML version. It seems to have to do a SaveAs
to get it to save as a XML (with the same file extension -which is weird).
Having now seen what using this file format does to my project file, I no
Click to expand...
longer want to save as XML ... :-(
 
Please submit a bug report (copied below) listing the effect the XML
format had on your project and how you were going to use the format in
your development of the device. This will provide leverage for me in
driving fixes and understanding where we can do better.
Thanks
Andy
This posting is provided "AS IS" with no warranties, and confers no
rights.
======================================
Bug Report / Suggestions for the Windows Embedded team.

E-mail this bug report or product suggestion to wecrt AT microsoft.com.
All suggestions or bugs will be added to the product team’s bug
database. If you require assistance in troubleshooting a problem with
your device or runtime, either post your question to the Microsoft
public newsgroup (microsoft.public.windowsxp.embedded) or contact
Microsoft Product Support Services
(http://support.microsoft.com/default.aspx?pr=cntactms&style=home).

Your Name:
(Optional)


Your e-mail address:
(Optional unless you want us to contact you):


XPe Version:
(Gold, SP1, SP2)


MUI Language Pack:
(N/A, English, Japanese, etc...)


Brief Bug Description or Product Suggestion:
(This is the Title of your Bug or Suggestion)


Detailed Bug Description or Product Suggestion:
(Be as detailed as possible, list hardware or software required to
repro the bug, etc...)


Steps to Reproduce the Bug:
(If applicable, please list the exact steps to repro the issue and be
as detailed as possible)


Additional Information:
(Paste sections of the FBA Log, the TD Build log, list of components,
etc…)
 
Thank you, feel free to mail that to the alias listed at the top of
that form, it'll wind up in our bug tracking DB from there. You're
welcome to send any bug anytime to that 'wecrt' alias.

Thanks again.
 
Hello Mark,

we are in hthe process of setting-up a configuration management (read
version control) infrastruture and have tried using SLXDiff (from Sean
Liming) for the purpose you once mentioned. Anyhow we have run into
limitations of that tool (such as not detecting differences between SLXes
that differ only in the values of the SLX's settings).

Hence we are considering complementing it with some other tools.

What is the 3rd party tool you mentionned in your previous post?

Best regards,
 
Hello Mark,

we are also in search of the adequate tools to support our version control
process, we are currently considering SLXDiff from Sean Liming's XPES toolkit
but need to complement it with some other tool.

What is that 3rd party tool you mentionned in your previous post?

Best regards,
 
Back
Top