<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Relink with new build options in ThinApp</title>
    <link>https://communities.vmware.com/t5/ThinApp/Relink-with-new-build-options/m-p/2647116#M7222</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I also would advise to always keep the original project (folder with package.ini and %...%-folders).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is much more powerfull and allows you to afterwards fix issues, that require updating settings (files, isolation mode, registry, settings in package.ini). The 'bit' of extra space needed with the new versions should not be the main issue btw. Switching to 'disk'-optimalisation (=compress) does have other negative effects, like additional CPU resources needed to unpack the required files. Be carefull not to pick the option that backfires in the long run...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And besides when you package tiny apps (like CMD) a few more MB for the package is not nice, but in general with nowadays storage capacities is not the biggest issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Michael Baars - Comprehensive ICT Solutions (NL)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #808080;"&gt;&lt;EM style="font-size: 8pt; "&gt;Please remember to mark the question answered if so and reward points to those who helped you...&lt;/EM&gt;&lt;/SPAN&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 05 Sep 2011 14:40:04 GMT</pubDate>
    <dc:creator>Theike</dc:creator>
    <dc:date>2011-09-05T14:40:04Z</dc:date>
    <item>
      <title>Relink with new build options</title>
      <link>https://communities.vmware.com/t5/ThinApp/Relink-with-new-build-options/m-p/2647111#M7217</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Is there any way to make relink with new build options?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need to add &lt;EM&gt;OptimizeFor=Disk&lt;/EM&gt; at least. Without this all the old packages become much bigger after relink.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Sep 2011 09:21:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Relink-with-new-build-options/m-p/2647111#M7217</guid>
      <dc:creator>NickOn</dc:creator>
      <dc:date>2011-09-02T09:21:30Z</dc:date>
    </item>
    <item>
      <title>Re: Relink with new build options</title>
      <link>https://communities.vmware.com/t5/ThinApp/Relink-with-new-build-options/m-p/2647112#M7218</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry no.. Relink will only update the runtime, license key and licensed to info.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Sep 2011 09:42:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Relink-with-new-build-options/m-p/2647112#M7218</guid>
      <dc:creator>pbjork</dc:creator>
      <dc:date>2011-09-02T09:42:08Z</dc:date>
    </item>
    <item>
      <title>Re: Relink with new build options</title>
      <link>https://communities.vmware.com/t5/ThinApp/Relink-with-new-build-options/m-p/2647113#M7219</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Too bad :smileyconfused:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any plans on it?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Sep 2011 09:58:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Relink-with-new-build-options/m-p/2647113#M7219</guid>
      <dc:creator>NickOn</dc:creator>
      <dc:date>2011-09-02T09:58:55Z</dc:date>
    </item>
    <item>
      <title>Re: Relink with new build options</title>
      <link>https://communities.vmware.com/t5/ThinApp/Relink-with-new-build-options/m-p/2647114#M7220</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not to my knowledge..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Sep 2011 10:28:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Relink-with-new-build-options/m-p/2647114#M7220</guid>
      <dc:creator>pbjork</dc:creator>
      <dc:date>2011-09-02T10:28:58Z</dc:date>
    </item>
    <item>
      <title>Re: Relink with new build options</title>
      <link>https://communities.vmware.com/t5/ThinApp/Relink-with-new-build-options/m-p/2647115#M7221</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you consider; relink is an option to updrage the ThinApp runtime in an existing package. So your package is not included in this process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Relink does not consider about your project file and settings. Its job is to upgrade the thinApp runtime inside your PDC without the customer required to recapture/rebuild.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now when you change some thing inside package.ini; it will only be considered in case of *rebuild*. So a relink will not act like rebuild.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 04 Sep 2011 09:32:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Relink-with-new-build-options/m-p/2647115#M7221</guid>
      <dc:creator>shrivastavaa</dc:creator>
      <dc:date>2011-09-04T09:32:08Z</dc:date>
    </item>
    <item>
      <title>Re: Relink with new build options</title>
      <link>https://communities.vmware.com/t5/ThinApp/Relink-with-new-build-options/m-p/2647116#M7222</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I also would advise to always keep the original project (folder with package.ini and %...%-folders).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is much more powerfull and allows you to afterwards fix issues, that require updating settings (files, isolation mode, registry, settings in package.ini). The 'bit' of extra space needed with the new versions should not be the main issue btw. Switching to 'disk'-optimalisation (=compress) does have other negative effects, like additional CPU resources needed to unpack the required files. Be carefull not to pick the option that backfires in the long run...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And besides when you package tiny apps (like CMD) a few more MB for the package is not nice, but in general with nowadays storage capacities is not the biggest issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Michael Baars - Comprehensive ICT Solutions (NL)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #808080;"&gt;&lt;EM style="font-size: 8pt; "&gt;Please remember to mark the question answered if so and reward points to those who helped you...&lt;/EM&gt;&lt;/SPAN&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 Sep 2011 14:40:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Relink-with-new-build-options/m-p/2647116#M7222</guid>
      <dc:creator>Theike</dc:creator>
      <dc:date>2011-09-05T14:40:04Z</dc:date>
    </item>
  </channel>
</rss>

