Observed problems with App.config.

Add-in Express™ Support Service
That's what is more important than anything else

Observed problems with App.config.
 
Oliver Engst


Guest


Hi everybody,

I observed some problems when I tried to implement the first Outlook AddIn.

When I added an App.config file to the project, it is named App.config in the project. The manifest file references it as "app.config". On my Visual Studio 2010 this was case sensitive and so it did not work for me. The second problem was that I expected the App.config to be automaically renamed to exefile.config or in this case dllfile.config and automatically being added to the output folder.

When I realized that the output folder will not contain this config file by default, I switched to "Copy always" in the "Copy to Output directory" setting.

This solved this problem and my outlook add in could use the config file. When I created a deployment project I came to the next problem that this App.config is in the Output Folder, but will not be added to the setup project when "Primary Output from Project" is added.

I would have expected the setup job to have all files included that are in the output directory.

Is this a behaviour by design or can I expect some changes here in the future?

Thanks in advance

HugoHiasl
Posted 16 Nov, 2010 07:47:10 Top
Eugene Astafiev


Guest


Hi Oliver,

When I added an App.config file to the project, it is named App.config in the project. The manifest file references it as "app.config".


1. Thank you for pointing this to us. We will fix it in the next builds of Add-in Express.

The latter two options you described above I can reproduce on my PC even with a regular windows forms application. This is by design which was born by Visual Studio ;-)
Posted 16 Nov, 2010 08:36:14 Top