views:

205

answers:

2

When I deploy applications to our biztalk server, we deploy to a test machine, add all the necessary resources, and then export an MSI that we import on our production servers (we have two). The other day, I noticed that there are dozens of folders on our production servers that appear to be copies of each developer's source code location. For example:

  • C:\Development\MyProject1
  • C:\Projects\SomeProject
  • C:\Users\Ryan\My Documents\Visual Studio Projects\Another Project
  • Many others

They're all projects we've deployed to Biztalk, and the folders don't contain source code, just the "Deployment" folder of each Biztalk project with DLL files in it. However, I thought the MSI packages were adding the DLL files to the GAC, or at the very least, were putting them in the MSI install target folder (all MSI files are installed to "C:\Biztalk\ProjectName").

Can somebody shed some light here? Are these extra copies safe to delete, and will that stop my Biztalk applications in their tracks?

+2  A: 

I wouldn't delete them until you did a redeployment. BizTalk is remembering the location the resource was initially added to the resource meta data source. For purpose of generating an MSI you should add the resources from where you want them to reside on the production server.

yieldvs
I'll bet that's exactly what's happening, though it's odd behavior - I'd expect every resource in the application to be deployed to the folder to which I'm installing the MSI, but this explanation makes sense. I'll try adding the resources from the "correct" folder and see what happens.
rwmnau
+1  A: 
Erik Westermann
Oddly enough, it seems that this only occurs with the resources added to the Biztalk application on initial deployment. If I add additional resources to the application post-vs-deployment and pre-msi-export, it automatically makes then "%BTAD_InstallDir%". Funny.
rwmnau