- This topic has 6 replies, 1 voice, and was last updated 9 years, 2 months ago by
.
-
Posts
-
-
Hi,
It seems to me that the BTSInstaller creates a package per Biztalk Project, meaning 1 BTSInstaller creates only 1 BiztalkProject. Is this right?
I currently has 4 Biztalk Projects(let’s just say BTProject1, BTProject2, BTProject3, BTProject4) which has different functionalities. I want to create only 1 package for them, meaning clicking 1 msi package would install those 4 bizalk projects. Is this possible?
Thanks,
Fred -
Hi,
I think BTSInstaller support Multiple Biztalk Project. I’ve tested it…
However I am encountering a new problem…
Consider this situation
BiztalkProjectA (which contains Orchestrations) calls BiztalkProjectB (which contains also orchestration) and both uses BiztalkProject C(which contains the schemas)
when I put BiztalkProjectA, BiztalkProjectB and BiztalkProjectC together in the BTSInstaller Package, it would BiztalkProjectA and B would not be deployed, only BiztalkProjectC is deployed, however if I took out BiztalkProjectA, then BiztalkProjectB and C will be deployed.
Do you guys know why this is happening?
Thanks in advance,
Fred-
-
Is there a possiblity that the installer compiles the project in the wrong order?
For example in my example above: BiztalkProjectA (which contains Orchestrations) calls BiztalkProjectB (which contains also orchestration) and both uses BiztalkProject C(which contains the schemas)
This means that BiztalkProjectC should be deployed first then BiztalkProjectB then BiztalkProjectA. Is there a possibility that the setup deployed the wrong BiztalkProject first thus error occurs? (Meaning BiztalkProjectC is deployed first then BiztalkProjectA then BiztalkProjectB).
If BiztalkProjectA is deployed first than BiztalkProjectB then an error may occur because BiztalkProjectA needs BiztalkProjectB to be deployed first…Is there anyway to make sure what BiztalkProject or dll needs to be deployed first?
Thanks
-
Hi lisa,
After looking at the log file that was produced by the installer, it seems to me that BTSInstaller wasn’t able to deploy the Biztalk Projects in the right order. I have made an alternative solution and that is to put one of the pre-requisite Biztalk Project dll on the Global Assembly Cache and somehow it worked but I still need to test this on other machine just to make sure that the effect is the same for all machines. I’ll let you know if it works on other machine.
Thank you very much 🙂
fred-
I had a similar problem just today. Seems like something gets \”stuck\” in memory when adding and removing things from the same installer package. Try nuking the old installer package altogether (delete the BTSInstaller project completely from under your project folder) and adding it back into your main project fresh from the SDK. If you have referenced everything properly in your main project then when you add it’s dll to the application folder it should automatically pull in the other 2 project dll’s.
-
There is a build order for projects contained within a solution – however it is not necessary to specify deploy order in the Installer since you are working with compiled objects. You will need to bind/start orchestrations in a particular order or if you were deploying them directly from the project – you would need to do this in a particular order, but with the installer it is not needed.
It sounds like you need one installer project – not several if the projects are interdependent. The rule of thumb should be – if they make one complete application – then they should be in one installer project.
First, copy the WHOLE BTSInstaller folder from the SDK folder into your main controlling project. Then add the BTSInstaller project as an existing item to that solution. Change all the properties as you like. Then you will need to Exclude a bunch of files that are not needed. Highlight all of the files listed in the application folder of the installer project EXCEPT BTSIAssemblyOrder.dll, BTSICustomAction.dll, btstd.xml, BindingSchema.xml.
Then you need to add each of the compiled project’s dlls into the application folder of the installer project – starting with the main controlling project dll. This should then automatically bring in the other referenced dlls automatically – but if it doesn’t – all them manually. If any of the projects are VB or C# code – then those should probably be added to a special folder – the Global Assebly Cache folder. The folder can be added to the installer project by right clicking the \”File System or Target Machine\” level in the installer and adding the \”special\” folder. Drag or add those assemblies into the GAC folder.
Build the the BTSInstaller project – then run it either through the provided Setup.exe or you can run it via command line with the option deploy = true – example: \”e:\\temp\\BTSInstaller.msi\” deploy=true
Hope this helps!
-
-
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.