Hi Christian,
Yes, use FilesToXmlPreprocess. When the MSI packages the itinerary XML files, they go into a folder named ESB. Unless you also use a folder named ESB in your BizTalk solution, you'll have to account for that difference between a "Server" and non-"Server" deployment. I didn't test it, but something along these lines:
If you prefer, you can use a conditional PropertyGroup for LocationPath instead of duplicating the entire item as I did here.
Thanks,
Tom
Yes, use FilesToXmlPreprocess. When the MSI packages the itinerary XML files, they go into a folder named ESB. Unless you also use a folder named ESB in your BizTalk solution, you'll have to account for that difference between a "Server" and non-"Server" deployment. I didn't test it, but something along these lines:
<ItemGroupCondition="'$(Configuration)' != 'Server'"><FilesToXmlPreprocessInclude="Itinerary1Master.xml"><LocationPath>..\Itineraries</LocationPath><OutputFilename>Itinerary1.xml</OutputFilename></FilesToXmlPreprocess></ItemGroup><ItemGroupCondition="'$(Configuration)' == 'Server'"><FilesToXmlPreprocessInclude="Itinerary1Master.xml"><LocationPath>..\ESB</LocationPath><OutputFilename>Itinerary1.xml</OutputFilename></FilesToXmlPreprocess></ItemGroup>
Thanks,
Tom