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 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
