Kyle, I dont think it is Package that caches the files, it is Shoes itself when it executes the code... but you are right that it is the files in \Documents and Settings\<username>\Local Settings\Temp\ that need to be deleted.
I can say this because I am packaging on OSX, then copying to XP... and deleting those files does indeed allow me to access the new code. Etienne On Thu, Feb 26, 2009 at 8:55 AM, Kyle King <[email protected]> wrote: > To force the packager to create a new exe when you modify the code, delete > all of the packager's temporary ruby files in > > \Documents and Settings\<username>\Local Settings\Temp\ > > The packager should really clean those up itself. > > Kyle > > On Feb 25, 2009, at 1:57 PM, Chaim Geretz wrote: > >> >>> its always the first exe I created that gets executed >> >> I saw this also on XP. Modified code, create .exe, original code >> launched. All done on XP. >> >> Wasn't sure if the problem was that the original .exe wasn't upgraded, >> or something was caching the app. Didn't pursue this any further. >> >> --Chaim >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of e deleflie >> Sent: Tuesday, February 24, 2009 10:58 PM >> To: [email protected] >> Subject: Package, cached exes and gem installs >> >> All, >> >> I've got 2 strange problems. I create a *.exe on OSX ... then I boot >> WindowsXP in parallels. From Windows, I access the mac hardrive and >> launch the *.exe. >> >> Strange thing is it doesn't matter how many times I create a new exe, >> its always the first exe I created that gets executed (I know because >> the shoes console announces the version of the shy inside the exe.). >> Something is caching the exe.... I dont know if its the Package >> function, or Shoes on Windows, or parallels when accessing a file from >> OSX. Has anyone else had this problem? >> >> In an attempt to work around this, I just create a *.shy file... and >> try to run that from windows. This time the new version is executed >> ... but now it says it "No such file to load 'mechanize'" ... despite >> the fact that I have : >> >> Shoes.setup do >> gem 'mechanize' >> end >> >> ... can anyone throw any light on these issues? >> >> Etienne > >
