<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Windows-Installer on Anything About IT</title><link>https://www.verboon.info/tags/windows-installer/</link><description>Recent content in Windows-Installer on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 05 Oct 2014 18:59:14 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/windows-installer/index.xml" rel="self" type="application/rss+xml"/><item><title>Analysing the file content of Windows Installer files using PowerShell</title><link>https://www.verboon.info/2014/10/analysing-the-file-content-of-windows-installer-files-using-powershell/</link><pubDate>Sun, 05 Oct 2014 18:59:14 +0000</pubDate><guid>https://www.verboon.info/2014/10/analysing-the-file-content-of-windows-installer-files-using-powershell/</guid><description>&lt;p&gt;A few weeks ago we have started with the preparation for introducing Microsoft Office 2013 and Internet Explorer 11. As with every introduction of new software it’s all about compatibility. During the course of testing applications we were informed that some of them caused an issue due to hard coded paths. Each application is going to be installed anyway so that application owners can conduct testing, but at the same time I thought, it would be nice if we could identify potentially affected applications upfront without having to go through an actual install.&lt;/p&gt;</description></item></channel></rss>