We have an application that, when published on TS08 as an .MSI packaged RemoteApp, does not do File Association like it's supposed to (even tho that box was checked when we made the MSI)...
It's a Clien-Server app; Client interface, looks for Databases on the back end; and it "requires" a T: drive mapping to the server containing the databases...
The icon on the desktop runs fine; but the PRODUCT of the App ("Jobs" let's call them) that have that icon's Extension (ES9) that you might also have on the desktop have that Windows icon that indicates it doesn't know how to open...
And when you double-click that Job icon (which, through File Association, should launch the App), you get an error saying something like, "...This is not a valid Win32 application"....
One more thing: While we were trying to fix this -- playing around with settings and so forth -- we somehow "broke" File Association on generic Apps (packages) like Word and Excel!!
Any ideas?
It's a Clien-Server app; Client interface, looks for Databases on the back end; and it "requires" a T: drive mapping to the server containing the databases...
The icon on the desktop runs fine; but the PRODUCT of the App ("Jobs" let's call them) that have that icon's Extension (ES9) that you might also have on the desktop have that Windows icon that indicates it doesn't know how to open...
And when you double-click that Job icon (which, through File Association, should launch the App), you get an error saying something like, "...This is not a valid Win32 application"....
One more thing: While we were trying to fix this -- playing around with settings and so forth -- we somehow "broke" File Association on generic Apps (packages) like Word and Excel!!
Any ideas?