Add-in Configuration File location

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

Add-in Configuration File location
ConfigurationManager is using winword.config for my add-in 
Bruce Mack




Posts: 5
 Joined: 2008-01-30
I ran into the same issue reported by Martin Bayly posted 02.11.2007 19:48:12. Sergey Grischenko posted "Ok. I will investigate this issue and will try to fix it in a new Add-in Express build." on 06.11.2007 11:22:20 and the thread ends there.
I'm using Version 3.6 (build 1879 Public Build) and I'm locked into using ConfigurationManager at this point. For now I'm just putting the config data into winword.config (office12) which didn't exist. I need a solution that will work with the click once deployment feature of Add-In Express for Office 2003 and Office 2007.

Thanks,
Bruce J Mack
Posted 30 Jan, 2008 14:43:47 Top
Sergey Grischenko


Add-in Express team


Posts: 7233
 Joined: 2004-07-05
Hi Bruce.

We didn't change anything in the loader configuration yet.
Do you need to store custom data into the add-in config file?
Posted 31 Jan, 2008 07:31:14 Top
Bruce Mack




Posts: 5
 Joined: 2008-01-30
Yes, we are using Enterprise library 3.1 in our backend tier which is also used by other applications in our product line. The ConnectionManager class is used to access the ConnectionStrings collection plus custom logging and exception handling policy settings. I am not permitted to change the backend tier libraries so I need another solution.

Thanks,
Bruce J Mack
Posted 31 Jan, 2008 10:29:35 Top
Sergey Grischenko


Add-in Express team


Posts: 7233
 Joined: 2004-07-05
Bruce, please try to use Xml classes (e.g. XmlDocument) to read the config. It is very simply in .NET. You can find some examples in MSDN help.
Posted 31 Jan, 2008 11:21:21 Top
Bruce Mack




Posts: 5
 Joined: 2008-01-30
I wish I could but the backend code is off limits. It's an unacceptable risk to change mission critcal code. My only other choice would be to create my own backend libraries. I have to many other work items I need to do (plus I hate code duplication). Release date is still a long way off so we got time to come up with something. I'm thinking it can be fixed in the click once deployment but I don't know if creating/updating winword.config is something we can get away with. I also need to get it working for office 2003.
Posted 31 Jan, 2008 11:56:01 Top
Sergey Grischenko


Add-in Express team


Posts: 7233
 Joined: 2004-07-05
Bruce,
where does your code expect the app.config file to be located?
Posted 31 Jan, 2008 12:39:25 Top
Bruce Mack




Posts: 5
 Joined: 2008-01-30
In the add-in config file. I use post build step to copy app.config to output folder renamed for use by the main add-in DLL (myaddin.dll.config). I also added the file to the setup app. This is a very common way to configure a DLL for add-ins and plug-ins where you don't have control of the main app config.
Posted 31 Jan, 2008 12:48:57 Top
Sergey Grischenko


Add-in Express team


Posts: 7233
 Joined: 2004-07-05
Hi Bruce.

Please download a new loader here:
http://www.add-in-express.com/projects/adxloader.zip

It works with the add-in config file. You just need to set the name of the config in the adxloader.dll.manifest file. Please see the example in the archive. Don't forget to re-register the project.
Posted 01 Feb, 2008 06:26:31 Top
Bruce Mack




Posts: 5
 Joined: 2008-01-30
Thanks, thats just what I needed.
Posted 01 Feb, 2008 14:40:50 Top
Yuri Astrakhan




Posts: 53
 Joined: 2006-05-19
Bruce, cross-posting from my question regarding the same topic:

Please note that the setup project does not automatically include proj.dll.config. The best way I found (that would both allow Visual Studio to modify it with wizards and not be dependent on which build configuration you choose to build) is to add the app.config file itself to the setup project and specify a different TargetName property to "proj.dll.config" name.
Posted 01 Feb, 2008 16:58:57 Top