E
erikjblair
Hi all,
This is a little in-depth, so bear with me. I have a client
application that uses the MS Config App block. Everything works as
expected under normal circumstances and the ConfigManager is able to
read items without problem when simply running the app.
Here's the issue. We have also entered a registry key
"HKEY_LOCAL_MACHINE\SOFTWARE\Classes\<MyAppName>\shell\open\command"
that allows us to go to the IE address bar and type
"MyAppName:<someargumentInfo>" and have it find our app. Problem is,
when the application is started from this method, the Config Manager is
unable to read any config data. It's confounding.
My thought is that it's because the App starts out in the IE process,
that the Framework isn't finding the App.Config file. When the App
starts out in it's own process, all is good.
Any ideas? Help!
Thanks!
Erik Blair
This is a little in-depth, so bear with me. I have a client
application that uses the MS Config App block. Everything works as
expected under normal circumstances and the ConfigManager is able to
read items without problem when simply running the app.
Here's the issue. We have also entered a registry key
"HKEY_LOCAL_MACHINE\SOFTWARE\Classes\<MyAppName>\shell\open\command"
that allows us to go to the IE address bar and type
"MyAppName:<someargumentInfo>" and have it find our app. Problem is,
when the application is started from this method, the Config Manager is
unable to read any config data. It's confounding.
My thought is that it's because the App starts out in the IE process,
that the Framework isn't finding the App.Config file. When the App
starts out in it's own process, all is good.
Any ideas? Help!
Thanks!
Erik Blair