New Post: Handling the log4net config file like the PortBindings Master file

Hi Jim,

I only used this approach in a BizTalk 2006 R2 environment and unfortunately the project was parked pending review so I never got to see it through to completion, that said, in the local development environment the approach appeared to be working perfectly.

Here is what I had in the BTDF Proj file (names changed to save any blushes):

<ItemGroup>

<FilesToXmlPreprocess Include="Organisation.BTSApp_Master.log4net">
  <LocationPath>..</LocationPath>
  <OutputFilename>Organisation.BTSApp.log4net</OutputFilename>
</FilesToXmlPreprocess>

</ItemGroup>

<ItemGroup>

<AdditionalFiles Include="Organisation.BTSApp_Master.log4net">
  <LocationPath>..</LocationPath>
</AdditionalFiles>

</ItemGroup>

and here is what was in the Organisation.BTSApp_Master.log4net file:
<!-- ifdef ${_xml_preprocess} --><!-- <connectionString value="data source=${ApplicationDB};initial catalog=Organisation_BTSApp;integrated security=true;persist security info=True" /> --><!-- else --><connectionString value="data source=(local);initial catalog=Organisation_BTSApp;integrated security=true;persist security info=True" />
<!-- endif --> The resulting Organisation.BTSApp.log4net contained my local development machine name rather than (local)…so as far as I can see it had worked, but as I said, I never got to take it onto a test environment via .msi and verify it worked correctly there.

Hope that helps. You've got me number, give me a call in the morning if you need anything further.

Cheers,


RedDwarf