G
Guest
Hello,
I have a smart client (Framework v1.1, No-Touch Deployment) application that
we have been using successfully for some time. We recently were testing some
of the offline capabilities of the app and ran into a serious problem. When
connected, the application launches flawlessly. However, if we try to launch
the application while "Working Offline" (no network connection), we get an
exception from IEExec.
In this offline launch scenario, all assemblies requried are in the download
cache. I have narrowed the problem down to the app.config file not being
accessible by the app in this scenario. I verified this by building the app
without the config settings and app.config file removed. In this case, the
application launched fine while the machine was offline. I put the config
file back in and the same problem arose.
So it seems to me that the <appname>.exe.config file is not being cached
properly and my question is how can I get this file to be cached and
available offline?
Any help is greatly appreciated.
Best Regards,
Tyler Foreman
I have a smart client (Framework v1.1, No-Touch Deployment) application that
we have been using successfully for some time. We recently were testing some
of the offline capabilities of the app and ran into a serious problem. When
connected, the application launches flawlessly. However, if we try to launch
the application while "Working Offline" (no network connection), we get an
exception from IEExec.
In this offline launch scenario, all assemblies requried are in the download
cache. I have narrowed the problem down to the app.config file not being
accessible by the app in this scenario. I verified this by building the app
without the config settings and app.config file removed. In this case, the
application launched fine while the machine was offline. I put the config
file back in and the same problem arose.
So it seems to me that the <appname>.exe.config file is not being cached
properly and my question is how can I get this file to be cached and
available offline?
Any help is greatly appreciated.
Best Regards,
Tyler Foreman