06-09-06 12:18 AM
Hi Doug,
My BizTalk solution has a configuration file. This file has details other
than biztalk configuration like user credentials, types of loads etc. The
dll's, which I have added as resources to this biztalk application from MMC
need to access this file to get the configuration information. Where this
Myconfig.XML lands up is driven by where the user installs it. So, if the
user installs it at c:\MyApp, the dll should look for path
c:\MyApp\Myconfig.xml and if the user installs it at c:\Program
Files\BizTalk, it should look at path c:\program Files\BizTalk\MyConfig.xml.
This is not required duing installation at all. This is required while the
application is running. For ex, when the orchestration kicks in, it calls th
e
methods in dll and the those methods need this configuration file. The way i
t
is done now is in the method, path is hard coded and when I install using th
e
MSI, I install it at the same path only.
I did try similar to what you said, but the path returned by the
GetAssembly.Location() returned me c:\windows\assembly\GAC_****\ which is no
t
useful.
-Milan
"Doug Girard [MSFT]" wrote:
> Can you elaborate on your scenario?
>
> Are you calling a post-processing script and looking to gain access to the
> My.ConfigFile.xml? If so, can you have this script be written to the same
> directory and just reference the file locally?
> string configPathName =
> Path.Combine(Path.GetDirectoryName(Assembly.GetExecutingAssembly().Locatio
n)
> , "MyConfigFile.xml"); // or something similar
>
> If I'm missing something, please explain more about what you are looking t
o
> do.
>
> Regards,
> Doug Girard [MSFT]
>
> Note: This posting is provided "AS IS" with no warranties, and confers no
> rights.
> --------------------
> The
>
>
[ Post a follow-up to this message ]
|