<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rss version="2.0">
  <channel>
  <title>microsoft.public.platformsdk.msi Google Group</title>
  <link>http://groups.google.com.au/group/microsoft.public.platformsdk.msi</link>
  <description>Microsoft Platform Software Development Kit newsgroup.</description>
  <language>en</language>
  <item>
  <title>Re: Control MsiInstallProduct return code?</title>
  <link>http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/521654205d77e2ed/b193bf80e8db275f?show_docid=b193bf80e8db275f</link>
  <description>
  What other types of results are you looking for? There&#39;s no reason custom &lt;br&gt; actions can&#39;t store status or extended info about what happened in the &lt;br&gt; registry. Success/failure/reboot is a consequence of the transactional &lt;br&gt; nature of the install - it either works or not. You have a say in what makes &lt;br&gt; it work or fail by using custom action return codes and so on.
  </description>
  <guid isPermaLink="true">http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/521654205d77e2ed/b193bf80e8db275f?show_docid=b193bf80e8db275f</guid>
  <author>
  ph...@wonderware.nospam.com
  (Wilson, Phil)
  </author>
  <pubDate>Fri, 06 Nov 2009 23:15:37 UT
</pubDate>
  </item>
  <item>
  <title>Control MsiInstallProduct return code?</title>
  <link>http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/521654205d77e2ed/85a0a964b3c32edb?show_docid=85a0a964b3c32edb</link>
  <description>
  Is there any way for an MSI package to control the return code from &lt;br&gt; MsiInstallProduct? I&#39;ve got a chainer that installs several MSI packages in &lt;br&gt; sequence, and I&#39;m looking for a simple way for packages to communicate a more &lt;br&gt; nuanced status than simply success/failure/reboot.
  </description>
  <guid isPermaLink="true">http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/521654205d77e2ed/85a0a964b3c32edb?show_docid=85a0a964b3c32edb</guid>
  <author>
  johnmcna...@discussions.microsoft.com
  (John McNamee)
  </author>
  <pubDate>Fri, 06 Nov 2009 18:36:08 UT
</pubDate>
  </item>
  <item>
  <title>Re: Minor upgrade as MSI on server with previous version of MSI &amp;</title>
  <link>http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/29bb513703f2d368/d9e5ee5938d22f9c?show_docid=d9e5ee5938d22f9c</link>
  <description>
  Nothing! That&#39;s the point - MSI will just do the right thing. &lt;br&gt; If you can find any documentation explaining that file overwrite rules &lt;br&gt; depend on file sequence, share it. The rules are here: &lt;br&gt; &lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://msdn.microsoft.com/en-us/library/aa367835(VS.85).aspx&quot;&gt;[link]&lt;/a&gt;
  </description>
  <guid isPermaLink="true">http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/29bb513703f2d368/d9e5ee5938d22f9c?show_docid=d9e5ee5938d22f9c</guid>
  <author>
  ph...@wonderware.nospam.com
  (Wilson, Phil)
  </author>
  <pubDate>Thu, 05 Nov 2009 19:23:45 UT
</pubDate>
  </item>
  <item>
  <title>RE: Minor upgrade as MSI on server with previous version of MSI &amp;</title>
  <link>http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/29bb513703f2d368/d7c7e00f3803f4db?show_docid=d7c7e00f3803f4db</link>
  <description>
  Additional note, I tried with REINSTALLMODE=vemus to replace even if file is &lt;br&gt; of equal version, I got following error &lt;br&gt; Error 1334.The file &#39;a.exe&#39; cannot be installed because the file cannot be &lt;br&gt; found in cabinet file &#39;Data1.cab&#39;. This could indicate a network error, an &lt;br&gt; error reading from the CD-ROM, or a problem with this package.
  </description>
  <guid isPermaLink="true">http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/29bb513703f2d368/d7c7e00f3803f4db?show_docid=d7c7e00f3803f4db</guid>
  <author>
  vb...@community.nospam
  (VishnuB)
  </author>
  <pubDate>Thu, 05 Nov 2009 17:44:03 UT
</pubDate>
  </item>
  <item>
  <title>RE: intercept or cancel ScheduleReboot</title>
  <link>http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/9baf91949521c015/6a638d6d88c2e9ca?show_docid=6a638d6d88c2e9ca</link>
  <description>
  Hi, &lt;br&gt; Windows Vista has Windows Installer 4.0 by default. For Windows XP SP3, I &lt;br&gt; think it&#39;s version 3.1. But you can always have the latest Windows &lt;br&gt; Installer setup package as a prerequisite to your setup. &lt;br&gt; Regards, &lt;br&gt; Jie Wang &lt;br&gt; Microsoft Online Community Support &lt;br&gt; Delighting our customers is our #1 priority. We welcome your comments and
  </description>
  <guid isPermaLink="true">http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/9baf91949521c015/6a638d6d88c2e9ca?show_docid=6a638d6d88c2e9ca</guid>
  <author>
  jie...@online.microsoft.com
  (&quot;Jie Wang [MSFT]&quot;)
  </author>
  <pubDate>Thu, 05 Nov 2009 08:14:27 UT
</pubDate>
  </item>
  <item>
  <title>Re: Minor upgrade as MSI on server with previous version of MSI &amp;</title>
  <link>http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/29bb513703f2d368/576e1d4d5803a2c8?show_docid=576e1d4d5803a2c8</link>
  <description>
  Thanks Phil, &lt;br&gt; I checked my pcp file, I set MinimumRequiredMsiVersion in Properties table &lt;br&gt; as 200 only. What value do you suggest for FileSequenceStart in ImageFamilies &lt;br&gt; table ? &lt;br&gt; But still I feel, file sequencing has some impact.
  </description>
  <guid isPermaLink="true">http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/29bb513703f2d368/576e1d4d5803a2c8?show_docid=576e1d4d5803a2c8</guid>
  <author>
  vb...@community.nospam
  (VishnuB)
  </author>
  <pubDate>Wed, 04 Nov 2009 18:25:31 UT
</pubDate>
  </item>
  <item>
  <title>RE: Minor upgrade as MSI on server with previous version of MSI &amp;</title>
  <link>http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/29bb513703f2d368/ceb54b918a982f89?show_docid=ceb54b918a982f89</link>
  <description>
  Hi Jie Wang, &lt;br&gt; Yes, we usually version the binaries same as Product version, in case of &lt;br&gt; 1.0.1.0 msp, a.exe was version ed as 1.0.1.0 and in new msi (2.0.0.0), a.exe &lt;br&gt; is 2.0.0.0 &lt;br&gt; Thanks, &lt;br&gt; Vishnu
  </description>
  <guid isPermaLink="true">http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/29bb513703f2d368/ceb54b918a982f89?show_docid=ceb54b918a982f89</guid>
  <author>
  vb...@community.nospam
  (VishnuB)
  </author>
  <pubDate>Wed, 04 Nov 2009 18:25:23 UT
</pubDate>
  </item>
  <item>
  <title>Re: Minor upgrade as MSI on server with previous version of MSI &amp; MSP</title>
  <link>http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/29bb513703f2d368/e0ea536a8f5122c2?show_docid=e0ea536a8f5122c2</link>
  <description>
  I agree with Jie Wang - you&#39;ve said nothing about actual *file* versions, &lt;br&gt; and these must be incremented for a patch or minor upgrade to replace them. &lt;br&gt; There&#39;s nothing in file sequencing that is related to replacing versioned &lt;br&gt; files on the system. &lt;br&gt; To avoid having to manually figure out sequencing in ImageFamilies use
  </description>
  <guid isPermaLink="true">http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/29bb513703f2d368/e0ea536a8f5122c2?show_docid=e0ea536a8f5122c2</guid>
  <author>
  ph...@wonderware.nospam.com
  (Wilson, Phil)
  </author>
  <pubDate>Wed, 04 Nov 2009 17:40:21 UT
</pubDate>
  </item>
  <item>
  <title>RE: Minor upgrade as MSI on server with previous version of MSI &amp; MSP</title>
  <link>http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/29bb513703f2d368/5c4c2c4bba25e17a?show_docid=5c4c2c4bba25e17a</link>
  <description>
  Hi Vishnu, &lt;br&gt; Could you confirm that the file a.exe itself is correctly versioned in all &lt;br&gt; versions? &lt;br&gt; Thanks, &lt;br&gt; Jie Wang &lt;br&gt; Microsoft Online Community Support &lt;br&gt; Delighting our customers is our #1 priority. We welcome your comments and &lt;br&gt; suggestions about how we can improve the support we provide to you. Please &lt;br&gt; feel free to let my manager know what you think of the level of service
  </description>
  <guid isPermaLink="true">http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/29bb513703f2d368/5c4c2c4bba25e17a?show_docid=5c4c2c4bba25e17a</guid>
  <author>
  jie...@online.microsoft.com
  (&quot;Jie Wang [MSFT]&quot;)
  </author>
  <pubDate>Wed, 04 Nov 2009 12:00:31 UT
</pubDate>
  </item>
  <item>
  <title>Re: Vista - User Directory</title>
  <link>http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/583c95063e9e4305/314885f64856d8cb?show_docid=314885f64856d8cb</link>
  <description>
  If per-user is OK, then that will always work, elevated or not. Issue then &lt;br&gt; may be that xml file will be installed to the per-user folder of the user &lt;br&gt; that is installing (could be an IT Admin) and not the user that will be &lt;br&gt; running it; in that case, user running it won&#39;t have the xml file! That&#39;s
  </description>
  <guid isPermaLink="true">http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/583c95063e9e4305/314885f64856d8cb?show_docid=314885f64856d8cb</guid>
  <author>
  d...@remove-this.dcsoft.com
  (David Ching)
  </author>
  <pubDate>Tue, 03 Nov 2009 23:58:08 UT
</pubDate>
  </item>
  <item>
  <title>Re: How to prevent &#39;program may have been uninstalled&#39; message in</title>
  <link>http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/c2c1afb97afb9fbf/98ebae693b98d6ef?show_docid=98ebae693b98d6ef</link>
  <description>
  As far as I know, the program is behaving as it should. After further &lt;br&gt; experimenting to try to discover why the error message is happening, I &lt;br&gt; discovered that it seems to have to do with our uninstalling of IIS. (We &lt;br&gt; install/uninstall IIS and ASP (or just ASP alone if IIS is pre-installed &lt;br&gt; without ASP) by launching a pkgmgr.exe command. Since uninstalling all of IIS
  </description>
  <guid isPermaLink="true">http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/c2c1afb97afb9fbf/98ebae693b98d6ef?show_docid=98ebae693b98d6ef</guid>
  <author>
  r...@discussions.microsoft.com
  (Rob)
  </author>
  <pubDate>Tue, 03 Nov 2009 21:10:03 UT
</pubDate>
  </item>
  <item>
  <title>Minor upgrade as MSI on server with previous version of MSI &amp; MSP</title>
  <link>http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/29bb513703f2d368/7a7e716454a0e7fb?show_docid=7a7e716454a0e7fb</link>
  <description>
  I have earlier version (1.0.0.0) of my product in .msi format and for that I &lt;br&gt; delivered patch as .msp with version 1.0.1.0. &lt;br&gt; I generated patch by comparing two msi&#39;s (1.0.0.0 &amp;amp; 1.0.1.0), where existing &lt;br&gt; binaries are modified, no new files added. &lt;br&gt; In PatchTemplate.pcp, I updated FileSequenceStart value in ImageFamilies
  </description>
  <guid isPermaLink="true">http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/29bb513703f2d368/7a7e716454a0e7fb?show_docid=7a7e716454a0e7fb</guid>
  <author>
  vb...@community.nospam
  (VishnuB)
  </author>
  <pubDate>Tue, 03 Nov 2009 19:11:01 UT
</pubDate>
  </item>
  <item>
  <title>Re: How to prevent &#39;program may have been uninstalled&#39; message in Vist</title>
  <link>http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/c2c1afb97afb9fbf/f1cacda38fbb80ee?show_docid=f1cacda38fbb80ee</link>
  <description>
  I have only seen this when the program faults in some way (or isn&#39;t actually &lt;br&gt; at the location pointed at by UninstallString). Is it possible that the &lt;br&gt; progam is faulting in that scenario?
  </description>
  <guid isPermaLink="true">http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/c2c1afb97afb9fbf/f1cacda38fbb80ee?show_docid=f1cacda38fbb80ee</guid>
  <author>
  ph...@wonderware.nospam.com
  (Wilson, Phil)
  </author>
  <pubDate>Tue, 03 Nov 2009 18:00:44 UT
</pubDate>
  </item>
  <item>
  <title>Re: Vista - User Directory</title>
  <link>http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/583c95063e9e4305/42a453bd61fb3e71?show_docid=42a453bd61fb3e71</link>
  <description>
  Hi David, &lt;br&gt; Thanks. I may have made it sound like I need access to all users, but I &lt;br&gt; don&#39;t if I get this right. I don&#39;t want to have to run elevated and &lt;br&gt; trigger the UAC. This came to a head when I was patching a new feature &lt;br&gt; and wanted to copy in that new xml. It copied without elevation but to &lt;br&gt; the wrong place. The wrong place happened to be all users. And if I were
  </description>
  <guid isPermaLink="true">http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/583c95063e9e4305/42a453bd61fb3e71?show_docid=42a453bd61fb3e71</guid>
  <author>
  a...@some.net
  (DanB)
  </author>
  <pubDate>Tue, 03 Nov 2009 17:03:32 UT
</pubDate>
  </item>
  <item>
  <title>RE: intercept or cancel ScheduleReboot</title>
  <link>http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/9baf91949521c015/dcff386bb123b641?show_docid=dcff386bb123b641</link>
  <description>
  I will try. Installer Services 4.0 are starting with Vista and XP SP3, right? &lt;br&gt; thanks &lt;br&gt; doc
  </description>
  <guid isPermaLink="true">http://groups.google.com.au/group/microsoft.public.platformsdk.msi/browse_thread/thread/9baf91949521c015/dcff386bb123b641?show_docid=dcff386bb123b641</guid>
  <author>
  docschn...@newsgroup.nospam
  (docschnipp)
  </author>
  <pubDate>Tue, 03 Nov 2009 16:02:07 UT
</pubDate>
  </item>
  </channel>
</rss>
