why do you think there's a problem Rick? send me your .wepm file and I'll have a look.
I'm sure the demo version has no restriction other than the time one. I'm not entirely sure if app central would have some restriction about uploading packages created by a copy of WE with no serial number; anyway, send me yoru .wepm file and we'll see. Chip -----Original Message----- From: RicksPlace [mailto:[email protected]] Sent: Saturday, April 23, 2011 5:50 AM To: [email protected] Subject: Re: How Can I tell if the vbs is associated with the we file after PackageManager create? Hi Chip: The file is straight forward. Both the vbs and xml files are there as items 0 and 1 respectively. They are also in the Script section and the association for 0 is to NOTEPAD.we. So that puppy looks good! So it has to be a problem subsequent to the PackageManager. I have verified that my App Central Uploads are getting processed by modifying data in the vbs file and even in the Package Manager then modifying the AppCentral entry and the changes took place so I think the Upload is working - although I can't yet verify the Packing File is getting uploaded or if it is correct yet. I am still leaning twoard my demo version being the problem but won't know until I hear from someone at GW or nail the actual place where this puppy is laying down on the job. Thanks for the help big time! That is exactly the type of analysis necessary to do this type of debugging and most other techniques involve guessing and what some call a shotgun approach to guesswork solutions which I don't like to do unless there is no other choice. Later: Rick USA ----- Original Message ----- From: "Chip Orange" <[email protected]> To: <[email protected]> Sent: Friday, April 22, 2011 9:27 PM Subject: RE: How Can I tell if the vbs is associated with the we file after PackageManager create? > 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 > >
