<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Make snapshots of filesystem and registry using command line</title><link>http://msmvps.com/blogs/martinzugec/archive/2008/05/14/make-snapshots-of-filesystem-and-registry-using-command-line.aspx</link><description>Some installers can be very mysterious - this suddenly applies for MSI packages, even using full logging, it is not easy to find out which registry keys or files were modified\deleted\added. If you have application that is using some custom installer</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>application installer</title><link>http://msmvps.com/blogs/martinzugec/archive/2008/05/14/make-snapshots-of-filesystem-and-registry-using-command-line.aspx#1622678</link><pubDate>Wed, 14 May 2008 22:34:13 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1622678</guid><dc:creator>application installer</dc:creator><description>&lt;p&gt;Pingback from &amp;nbsp;application installer&lt;/p&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1622678" width="1" height="1"&gt;</description></item></channel></rss>