No-Touch Deployment app.config problem

[John N]

I'm having a very frustrating problem with a no-touch-deployed
application and its app.config file. When it loads from a remote
server, it cannot get any settings from the app.config file. In trying
to locate the problem, I have tested the following things:

1. The application works flawlessly when deployed via XCopy.
2. The application works flawlessly when accessed on my own machine
via http://localhost.
3. The app.config file is accessible. I can browse to it manually and
download it.
4. The app.config file is being downloaded by the application and
stored in the IE browser cache, but is still not accessible to the
application.
5. Another application - a simple one for testing this situation -
exhibits exactly the same behaviour.

I have already removed the *.config mapping from IIS for the relevant
directory, and, just like before, the app.config is still accessible.
I have enabled anonymous access. Just like before, the app.config is
still accessible.

I have thus concluded that the problem is not with my server
configuration.

Is anyone able to offer any insight into the situation? Anyone else
encountered this problem?

John N

 

[Guest]

Hi Joh

The config files will always get downloaded to Temporary Internet Files folder where as the rest of your Application's assemblies will go into the APpliction Data folder, when you download them using No Touch Deployment. This is known problem, and as far as i know there is no direct solution for this, but definitely a work around... I have put in the same here...see if this helps you..

1. Designed a web service, and make this web service return a datatable which will contain the configuration data.
2. On the client application call this web service first, get the datatable which contains the configuration data. if required serialize it, else maintain the datatable, in memory and use it in the application

Hope this helps...If you get any good solution for this...please let me know...mail me at (e-mail address removed)

Thanks
Ramjee Tangutu
Microsoft India Community Sta






----- John N wrote: ----

I'm having a very frustrating problem with a no-touch-deploye
application and its app.config file. When it loads from a remot
server, it cannot get any settings from the app.config file. In tryin
to locate the problem, I have tested the following things

1. The application works flawlessly when deployed via XCopy
2. The application works flawlessly when accessed on my own machin
via http://localhost
3. The app.config file is accessible. I can browse to it manually an
download it
4. The app.config file is being downloaded by the application an
stored in the IE browser cache, but is still not accessible to th
application
5. Another application - a simple one for testing this situation
exhibits exactly the same behaviour

I have already removed the *.config mapping from IIS for the relevan
directory, and, just like before, the app.config is still accessible
I have enabled anonymous access. Just like before, the app.config i
still accessible

I have thus concluded that the problem is not with my serve
configuration

Is anyone able to offer any insight into the situation? Anyone els
encountered this problem

John

 

[John Vottero]

I'm having a very frustrating problem with a no-touch-deployed
application and its app.config file. When it loads from a remote
server, it cannot get any settings from the app.config file. In trying
to locate the problem, I have tested the following things:

1. The application works flawlessly when deployed via XCopy.
2. The application works flawlessly when accessed on my own machine
via http://localhost.
3. The app.config file is accessible. I can browse to it manually and
download it.
4. The app.config file is being downloaded by the application and
stored in the IE browser cache, but is still not accessible to the
application.
5. Another application - a simple one for testing this situation -
exhibits exactly the same behaviour.

I have already removed the *.config mapping from IIS for the relevant
directory, and, just like before, the app.config is still accessible.
I have enabled anonymous access. Just like before, the app.config is
still accessible.

I have thus concluded that the problem is not with my server
configuration.

Is anyone able to offer any insight into the situation? Anyone else
encountered this problem?

You didn't tell us what problem you're seeing. Is an exception being
thrown? Are you getting null values back? What's going wrong? What do you
mean by "not accessible to the application"?

When you say "app.config", you really mean "appname.exe.config", right?

If you're trying to configure remoting via a config file, it won't work.

I do have no-touch deployment working an retrieving values from a config
file so, it is possible.

John V