biztalkdeployment Forum Rss Feed

New Post: BTDF PATH environment variable for BTSTask?

tfabraham — Fri, 24 May 2013 21:42:13 GMT

Excerpt from my 64-bit BizTalk 2010 machine PATH:
C:\Program Files (x86)\Microsoft BizTalk Server 2010\;C:\Program Files (x86)\Microsoft BizTalk Server 2010\Bins32;C:\Program Files (x86)\Microsoft BizTalk Server 2010\Bins64;

I'm guessing that you did not restart Visual Studio after you modified the PATH, because it will have a copy of the environment variables from the time it started up. I'm assuming that you're just running a deploy from Visual Studio. If you have the above in your PATH and restart VS it should work OK.

Thanks,
Tom

New Post: BTDF PATH environment variable for BTSTask?

Ritley57 — Fri, 24 May 2013 20:15:22 GMT

I recently installed openSSH on my machine which subsequently overwrote my entire PATH environment variable string.

I've since put everything I could think of back in, including BTSTask.exe. I can run BTSTask manually just fine but when I try to use BTDF to deploy anything I get the following error:

DeployAppDefinition:
BTSTask.exe AddApp -ApplicationName:"CHN.ASO.HealthX" -Description:"CHN.ASO.HealthX"
'BTSTask.exe' is not recognized as an internal or external command,
operable program or batch file.

Does BTDF create its own PATH env var when installed? Anyone know how to fix this?

New Post: Include file in outdir, but not in Msi

adrach87 — Thu, 23 May 2013 03:21:02 GMT

This worked, once I got the correct path for the file I wanted to copy.

Thanks.

New Post: Include file in outdir, but not in Msi

tfabraham — Wed, 22 May 2013 06:33:49 GMT

On BizTalk 2010 and newer you can use:

  <Target Name="CopyFilesToTargetDir" AfterTargets="Installer">
    <CreateItem Include="..\..\MsiDeploy.bat">
      <Output TaskParameter="Include" ItemName="CopyPostInstaller" />
    </CreateItem>

    <Message Text="CopyPostInstaller = '@(CopyPostInstaller)'" />
    <Message Text="TargetDir = '$(TargetDir)'" />

    <Copy DestinationFolder="$(TargetDir)" SourceFiles="@(CopyPostInstaller)"/>
  </Target>

See if the Message tasks write something out and whether the values are valid. It is not easily possible to modify the .bat file contents on initial creation.

Thanks,
Tom

New Post: Batching the installs

tfabraham — Wed, 22 May 2013 06:27:15 GMT

The MSI build just uses the WriteLinesToFile MSBuild task to write the bat file using File="@(InstallBatFile)". You could certainly use that or any other MSBuild task to modify or overwrite the bat file with your own.

If you're on BizTalk 2010 or newer, you can add <Target Name="UpdateBatFile" AfterTargets="Installer"></Target> to the bottom end of your .btdfproj and add the necessary task(s) inside it.

Thanks,
Tom

New Post: Include file in outdir, but not in Msi

adrach87 — Wed, 22 May 2013 04:12:27 GMT

I updated to use an absolute path but that didn't work either. I even tried using msbuild and pointed it to the CustomPostInstaller target to determine if it maybe it just wasn't running that target, but again nothing. I also don't see any errors or warnings about not finding the MsiDeploy.bat file, so I don't think it's the path.

One other possibility to get the file I need would be to customize the Install-ProjectName-Version.bat file. Is that possible?

Thanks for your help.

New Post: Batching the installs

LDeckers — Tue, 21 May 2013 10:10:19 GMT

When the msi gets created, a linked bat file is also created.
Is it possible to append this bat file so that when a new version of the msi gets created, the batfile is also correclty filled out.

This way the full deployment of the biztalk project could be automated (including creating Environment Variables and creation of directories etc.)

New Post: Include file in outdir, but not in Msi

tfabraham — Tue, 21 May 2013 06:35:17 GMT

Yes. Then I would assume that the path to MsiDeploy.bat is incorrect. The path is relative to the Deployment project folder. Try a full explicit path if you can't get a relative path to work, just to see if you can get the file copied.

Thanks,
Tom

New Post: Include file in outdir, but not in Msi

adrach87 — Mon, 20 May 2013 16:14:21 GMT

Thanks, but that doesn't seem to be working for me.

This goes in the btdfproj file, in the Project element, right? The CreateItem node is underlined with the message "Target element has invalid child element CreateItem. List of possible elements expected: Task, PropertyGroup, ItemGroup, OnError".

When I build an MSI, it works as normal, but the MsiDeploy.bat doesn't show up in the \bin\release folder.

New Post: BTDF and Visual Studio 2012

nikolaiblackie — Sun, 19 May 2013 06:48:53 GMT

Agreed Bryan, thanks team for continuing to support the community, greatly appreciated.

New Post: BTDF and Visual Studio 2012

bryanmeek — Sun, 19 May 2013 06:36:46 GMT

thanks, appreciate you continuing to upgrade/support this great tool.

New Post: BTDF and Visual Studio 2012

tfabraham — Sun, 19 May 2013 06:30:06 GMT

Please upgrade to the v5.1 release available for download here.

New Post: Include file in outdir, but not in Msi

tfabraham — Sun, 19 May 2013 05:18:32 GMT

Use this:

  <Target Name="CustomPostInstaller">
    <CreateItem Include="..\..\MsiDeploy.bat">
      <Output TaskParameter="Include" ItemName="CopyPostInstaller" />
    </CreateItem>

    <Copy DestinationFolder="$(TargetDir)" SourceFiles="@(CopyPostInstaller)"/>
  </Target>

Thanks,
Tom

New Post: Include file in outdir, but not in Msi

adrach87 — Fri, 17 May 2013 21:17:06 GMT

I have a need to copy a batch file from the Deployment folder to the outdir while building the MSI installer. Normally I'd just set Copy to Output folder to true in VS, but since the deployment framework isn't a project template, I don't have that option.

I tried creating a postbuild action that just copies the file, but that doesn't seem to be executed. Here's how I set that up:

  <ItemGroup>
    <PostBuildEvent Include="MsiDeploy.bat">
      <Command>xcopy ..\..\MsiDeploy.bat .</Command>
    </PostBuildEvent>
  </ItemGroup>

But even after creating the MSI all I get are the ProjectName-Version.msi and Install-ProjectName-Version.bat files. What am I missing?

New Post: Adding new DLL into already deployed app

tfabraham — Thu, 16 May 2013 19:03:10 GMT

Hi and welcome!

Yes, that should work fine. Essentially you are bypassing the build-deployment process by directly updating files on the server in the installation folder. By the same token, if you copy new DLL's to the server as you are describing, you may also copy a new .btdfproj to the server. If the new .btdfproj references an additional assembly then it will be picked up during the redeploy. I'm assuming that you are rebuilding the application and specifically copying all necessary updated DLL's to the server.

There are some scenarios where you may have an issue on the undeploy part of the redeploy depending on how and what you change in the .btdfproj, but worst case if you encountered a problem you would just need to undeploy first, then copy and overwrite the .btdfproj and DLL's, then deploy again.

Thanks,
Tom

New Post: Adding new DLL into already deployed app

Nib75 — Thu, 16 May 2013 15:37:01 GMT

Hello

I'm new here, and first of all I would like to thanks you about this framework, even if I used half of the features actually.

Here is my "problem":
I have an existing solution deployed / installed into my client environment (BDTF).

I use in general the re-deploy option in order to update the existing DLL when I make a change in it. I replace the DLL into the \Program file\ folder, and my DLL is refreshed into BT and the GAC and then redeploy option. This avoid human error in hotfix deployment procedure (such as forget to restart host instance etc...).

Now I wants to use the "redeploy" in order to add a new DLL, is it possible to do it by updating deployment definition for example ? (Goal is to do not re-delivered the whole BTDF project)

Please let me know if my requirement is clear.

Thanks in advance

Regards

New Post: Avoid Application shortcut appearing in start menu during MSI installation

keshpras — Wed, 15 May 2013 05:47:14 GMT

Thanks a lot Tom for the information. Eagerly looking for the next release. TC.

Cheers
Keshav

New Post: Avoid Application shortcut appearing in start menu during MSI installation

tfabraham — Tue, 14 May 2013 17:28:06 GMT

Hi Keshav,

v5.1 Beta 2 is feature complete, so I'm just waiting to see if anyone finds any critical issues. Maybe a few more documentation updates. Otherwise I'm just letting it rest for 3-4 weeks and if nothing critical comes up, then Beta 2 will essentially become the official v5.1.

Thanks,
Tom

New Post: Avoid Application shortcut appearing in start menu during MSI installation

keshpras — Tue, 14 May 2013 05:47:03 GMT

Hey Tom

Thanks for your reply.
Wow, thats awesome! By the way, when can we expect v5.1 release? Any time frame (need not have to be accurate).

Cheers
Keshav

New Post: Have specific ports only appear in a specific environment

tfabraham — Tue, 14 May 2013 04:25:08 GMT

Great, glad to hear it. Thanks for the positive feedback -- it's always great to hear!

Tom