sorry, meant to say it's a .cab file, not a .zip file, but your decompression utility should handle it just the same.
Chip -----Original Message----- From: Chip Orange [mailto:[email protected]] Sent: Friday, April 22, 2011 9:23 PM To: [email protected] Subject: RE: How Can I tell if the vbs is associated with the we file after PackageManager create? Hi Rick, congrats on getting this all figured out in one day! I just got home and read my email (can't read the GW lists from my work email, they don't agree with one another on email formats), so I'm just learning of your trials. here's an interesting tidbit: a .wepm file is actually a zip file. if you want to verify things, just change it's extension to be .zip, and then have a look at it's contents. in addition to your files there will be two extra files, both of which have no extension, but which are text files. the one named wepackinglist will give you info about your package; including, if it's associated with something, some lines like the below (borrowed from procedure finder): [ProcFind.vbs] assoc0=notepad.we this is a nice way to reassure yourself you did everything right, and got all your files in, and so on. hth, Chip ________________________________ From: RicksPlace [mailto:[email protected]] Sent: Friday, April 22, 2011 1:06 PM To: [email protected] Subject: Re: How Can I tell if the vbs is associated with the we file after PackageManager create? Hi Jeff: OK, that appears to be the case when I open PackageManager, type in the name and select the vbs file in the list of files to include. The Associate box, if I open it, has the NotePad.we file in the box. I guess I will try and upload the wepm file to app central, unload the app in my app manager, remove it from the Default folder and try downloading it again to see if it installs completely. Thanks Jeff: Rick ----- Original Message ----- From: Jeff Weiss <mailto:[email protected]> To: [email protected] Sent: Friday, April 22, 2011 12:22 PM Subject: Re: How Can I tell if the vbs is associated with the we file after PackageManager create? When you open package manager and choose to modify your existing package, then open Notepad2011.wepm, you can see your association. In order to see your association, you need to select the Notepad2011.vbs file from the file list in the package manager. This is the file that is associated, and the buttons showing the association only work when the .vbs file is selected. Hope this helps, Jeff Weiss ----- Original Message ----- From: RicksPlace <mailto:[email protected]> To: [email protected] Sent: Friday, April 22, 2011 9:36 AM Subject: How Can I tell if the vbs is associated with the we file after PackageManager create? Hi: I have associated the vbs to the we many times and clicked the create file yet the next time I bring up the Package Manager the association buttons are disabled until I select the vbs file and then they are enabled and the NotePad.we file is in the associate file. I opened the Notepad.we file in text mode and script1 is set to NotePad2011.vbs so the we file thinks it is associated. Is there some way I can confirm the association is valid before I start trying to upload things to app central again? By the way, I am not suppose to include the Notepad.we file in the list of files to include in the package itself along with the NotePad2011.vbs and NotePad2011.xml files am I? If I can confirm the association is valid and in place i will upload and rename my local vbs and xml files and try another download / install from app central to see if it is automatically loaded and started in AppManager. Thanks: Rick USA
