Rick, let me just point out something you may or may not understand:
when you make an updated version you need to do all of these things: * edit the xml and change the value of the version number for the app, which it usually puts into a string. (if you aren't getting your version number from the xml file, then you'll need to change the lines of code in the .vbs file instead). * edit the package and change the version number it stores in it's own field to match that you just put in the xml file. now add new copies of both the .vbs file and the .xml file to your package, and save it. * now go to app central and edit your entry for this app. change the version number app central stores in it's own field to match the other two just mentioned. it pops up a dialog when you go to leave the version number field asking if it's ok to reset things related to the current version, and you should always choose "ok" here. * enter your info about the reason for the update in the appropriate field on this app central page, and upload the new .wepm file. choose the "update" button. you should get a message on the next page that both your app (page) and file have been updated. So, your version number has to be updated, and has to be the same, in 3 different places: the xml, the .wepm file, and the app central page. hth, Chip -----Original Message----- From: RicksPlace [mailto:[email protected]] Sent: Saturday, April 23, 2011 8:54 AM To: [email protected] Subject: Re: How Can I tell if the vbs is associated with the we file after PackageManager create? Hi Vic: OK, I just spent a couple of fun hours going through some auto-generated html. Here is what I have found from that and testing. When a modification is made to a script and then you go to App Central and click the update button, I forget what it was actually labeled kind of burned around the edges, the App Central page passes the values but not any new files to the App Central Server. The actual .vbs, xml and the rest of the files reside on their server. So, It would appear that the modifications I am making to App Central's website are getting changed and passed to the App Central server. The change in the version number of the App Central page itself is indicative of this. However, for whatever reason either the App Central page is not passing the value required to trigger the App Central server to go out and pick up the new version of the wepm file or there is something in the code on their server that is blocking the server from going out to pick up the new version of the wepm file. I have not yet done a test by changing the xml or vbs files to determine if they are getting updated by the App Central server. One other thing, I checked the box to send me a e-mail upon any change to my project but I never get any e-mails which might also support the notion that the files are not getting updated on the App Central server. I did not see a java script to send this e-mail, although I admit I didn't look too hard for it since I was looking for how the wepm file was handled, which may mean the e-mail would be sent by the server as well. thus, the server is either not getting the update request from the App Central page or, again, something on the server is blocking or not handling the update. If there is an error at the server it is not getting posted back to the App Central WebPage so far as I can tell so I am in the dark since the problem seems to be between the GW Website and the GW Server. The only thing I can think of would be to remove the app from App Central and ReCreate it on App Central to see if it Refreshes the GW App Central Server.Before I try that I might run another update with changes to the vbs and xml and wepm files and this time browse to my wepm file instead of just hitting the update button. Perhaps the site does not update anything except the actual site contents unless we pick a new file even if the file name and path are the same as when the App Central Server created the Package to actually download. I would have thought from the wording that the file and path would be maintained on the App Central Server unless changed on the App Central Edit page but this test might tell me if that is the case. If neither test results in the answer then I think I will have to ask for some help from the GW guys who have access to the server side code. So that is where I am at: First I will update everything so I can tell what I get downloaded, then I will browse to my wepm file on the App Central Page and try a update. If that does not work I will do a complete ReBuild of my account and the adding of my app to App Central to see if that works. I am tired, it's the Easter Weekend and my wife is harping on me to spend time with her so I might not get at this until Monday. Later Guys and Happy easter! Rick USA ----- Original Message ----- From: "Vic Beckley" <[email protected]> To: <[email protected]> Sent: Saturday, April 23, 2011 7:12 AM Subject: RE: How Can I tell if the vbs is associated with the we file after PackageManager create? > Rick, > > I don't know what is going on. I just downloaded the package again > from App Central. The App Central page claimed it was version 0.1. > When I installed it, it stated it was version 00 and was not > associated with Notepad. The wepackinglist file shows version 00 and > does not include the association line. If you are getting it saved > correctly, somehow it is not getting uploaded right. The wepackinglist > file is dated 4/22/2011 at 9:31 AM. I really don't think your demo > would affect this, but I am at a loss to help any further. > > One other thing, you might want to put a more descriptive explanation > of what the app does in the description edit box in Package Manager. JMO. > > Vic > > > -----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 >> >> > >
