Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Dealing with application updates in Windows 7
Message
 
 
To
All
General information
Forum:
Visual FoxPro
Category:
Installation, Setup and Configuration
Title:
Dealing with application updates in Windows 7
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
MS SQL Server
Miscellaneous
Thread ID:
01481764
Message ID:
01481764
Views:
181
After reading multiple threads here, Doug Hennig’s Advisor article “Developing Microsoft Visual FoxPro Applications for Windows Vista” , Calvin Hsia’s blog and several MSDN resources, I still have questions about the application update process for Windows 7. I only have XP here so hope someone can fill in some blanks so that I can get a couple of install packages out this weekend.

All of the applications install into their own directory, rather than under program files. I plan to add a manifest that includes
requestedExecutionLevel level="asInvoker"
to prevent ‘virtualization’ by Windows. Does the manifest also suppress the UAC dialog for the copy or ShellExecute() command that actually copies the new version of the app to the local drive? It would definitely be better if the users didn't see that dialog.

The current update file uses the Run command to launch the app after the copy (if needed.) This allows the desktop shortcut to reference the same file whether updating is required or not. Will this still work with Windows 7?
Next
Reply
Map
View

Click here to load this message in the networking platform