PDA

View Full Version : XML or Binary



rdemarco
11-30-2005, 06:35 PM
Hi,

Just wondering if there is a preferred method of saving the project as XML or Binary? I've just worked out that you need it stored as Binary to use Windows Automation.. Is there any reason apart from this that you would save the project in a particular format?

Thanks, Rick

MartinMarkevics
11-30-2005, 06:47 PM
Among other things, the XML format allows for a better experience with source control. Since the file is text, you can easily do diffs to see what changed over time. You can't do that with the binary format.

On a side note, the InstallShiled automation layer works with both formats. I'm not sure what exactly you are doing with the MSI automation, but perhaps the same can be accomplished with the IS automation, which would allow you to use the XML format.

rdemarco
11-30-2005, 07:14 PM
Thanks Martin..

I am trying to change Path Variables using Windows Automation. Can you do this with InstallShield automation? I found this article which explained how to do it - http://www.installshield.com/news/newsletter/0402-articles/modify.asp

Thanks, Rick

sks2004
11-30-2005, 10:11 PM
XML is great for source control diff'ing, no doubt about it.

Take a look at this: http://community.macrovision.com/showthread.php?t=151561

Hamilton-Scott
12-01-2005, 03:49 AM
There is no problem using XML with the automation objects. I have a VB app that does all the last-minute stuff and builds and I've not had a problem. Only thing I did notice is that loading the project does take longer. That's to be expected given the conversion process and hoops it has to jump through converting XML into internal COM table format. As remarked, use XML for SourceUnsafe.

sks2004
12-01-2005, 11:55 AM
...you must be using the automation interface (COM)...which works for many things (definatly not all!) not writing directly to the ISM (project) file, per-build.

I too set numerous values per different build configs, via the IS automation interface...couldn't do without it. But some methods are buggy, and need to be done directly to the MSI...post-build, via Windows Installer automation interface (COM).

MartinMarkevics
12-05-2005, 04:24 PM
Which methods are "buggy"? Let us know and we'll fix them.

Christopher Painter
12-05-2005, 04:38 PM
Also when using XML format you can use XML DOM to manipulate the project in case there is something that can't be done through the project automation interface. ( The automation interface would be considered safer though.) You don't have to do it through WindowsInstaller.Installer as a post build step.

sks2004
12-05-2005, 06:19 PM
I have submitted a list of these issues and others to support, and even received a notice that they were replicated.

http://community.macrovision.com/showthread.php?t=151561