I have an external .dll that I want to refer in my custom pipeline component, if I refer in my .cs proj and when I build it is generating 2 .dll in bin folder.

And when I refer this .cs proj in my Pipeline proj and run a build it always throwing error 'the process is being used by another process already'.

What am I doing wrong ? How can I correct this ?

in BTDF file, I am doing as below :

 <PipelineComponents Include="$(ProjectName).dll">
      <LocationPath>..\ProjName\bin\$(Configuration)</LocationPath>
    </PipelineComponents>

Hi,

Set <IncludePipelineComponents> to true and add an ItemGroup (like Schemas) named PipelineComponents.  Hopefully you added the pipeline component to a separate assembly from the rest of your artifacts.

I have a separate .dll that I am referring named 'Ionic.zip' for me to include in my .cs proj. But when I am building, it is creating 2 dll (Ionic.zip.dll and project.dll) in bin folder.

And when I am referring this , in my Pipeline project, as mentioned earlier ''the process is being used by another process already'. what I am doing wrong here ? How should I refer the external dll ?

Hi Jag,

If your solution includes  projects with source code for .NET helper assemblies example Ionic.zip DLL, then put them under a ItemGroup Components.  If .NET assemblies that do not have projects with source code and they need to be installed in the GAC, then put them under ExternalAssemblies.

Assemblies containing custom .NET components

The Components ItemGroup is appropriate for any assembly that contains custom .NETcomponents (classes).  The assembly must contain only .NET artifacts.

<ItemGroup>

  <Components Include="MyComponents.dll">

    <LocationPath>..\$(ProjectName).Components\bin\$(Configuration)</LocationPath>

  </Components>

</ItemGroup>

Include attribute: DLL file name

Regards,

Sharad

HI,

Use Item group to add external assembly in BTDF like below

<ItemGroup>
    <ExternalAssemblies Include="Assembly1.dll">
        <LocationPath>..PathToAssembly</LocationPath>
    </ExternalAssemblies>
    <ExternalAssemblies Include="OtherAssembly.dll">
        <LocationPath>C:SharedAssemblies</LocationPath>
    </ExternalAssemblies>
</ItemGroup>

Thanks

Abhishek

do I need to place this 'Ionic.Zip.dll' and particular location ? or I can place that anywhere inside my project folder and refer that dll in my .cs proj to zip file ?

Place Ionic.zip dll in a folder and then refer it from the same folder (I don't think it much depends on the location from where you refer it).

<ItemGroup>
    <ExternalAssemblies Include="Ionic.zip">
        <LocationPath>..\Libraries</LocationPath>
    </ExternalAssemblies></ItemGroup>

Here Libraries folder contains your Ioniz.zip file and you can refer the Ioniz.zip from this folder to your cs project.

Regards,

Sharad

when I build the solution, I am getting following error ? 'ZipEncoder.dll ' is my .cs project build dll

Error	118	Unable to copy file "obj\Debug\ZipEncoder.dll" to "bin\Debug\ZipEncoder.dll". The process cannot access the file 'bin\Debug\ZipEncoder.dll' because it is being used by another process.	

Can you do the above process for ZipEncoder.dll as well now this one is missing.

Regards,

Sharad

<ItemGroup>
    <ExternalAssemblies Include="Ionic.Zip.dll">
      <LocationPath>..\$(ProjectName)</LocationPath>
    </ExternalAssemblies>
    
    <PipelineComponents Include="ZipEncoder.dll">
      <LocationPath>..\$(ProjectName)\bin\$(Configuration)</LocationPath>
    </PipelineComponents>
  </ItemGroup>

This is correct location for ZipEncoder.dll can you please verify this??

It is not taking this path. Try loading it from the same folder from which you are loading and able to GAC Ionic.zip Dll.

Regards,

Sharad

• Edited by SharadVerma 12 hours 1 minutes ago better

I see ZipEncoder.dll is in GAC but Ionic.Zip.dll is not present. May be that is the reason its failing.

Why my External assembly is not picking ?

If you go to the pipeline designer and choose the Add Item function in the Toolbox, it should automatically show up under the BizTalk Pipeline Components tab once the DLL is present in the BizTalk PipelineComponents folder.  So you would just deploy once, then create your pipeline.

Now, due to Visual Studio's big issues with DLL locking, there is never a great way to work with references in the pipeline designer.  I sometimes add a project reference to my PipelineComponents project, sometimes let the Add Item dialog add a reference to BizTalk's PipelineComponents folder.  Either way, you will probably run into at least some issues with that DLL being locked by Visual Studio.  Particularly whenever you have opened the pipeline designer.

Regards,

Sharad

Are you sure you are following this steps carefully

1. Set the IncludePipelineComponents property to true

The property may be included in any PropertyGroup, but is commonly placed in the first PropertyGroup in the project file.

<PropertyGroup>

 ...

 <IncludePipelineComponents>true</IncludePipelineComponents>

 ...

</PropertyGroup>

2. Add a PipelineComponents ItemGroup

<ItemGroup>

 <PipelineComponents Include="$(ProjectName).PipelineComponents.dll">

   <LocationPath>..\PipelineComponents\bin\$(Configuration)</LocationPath>

 </PipelineComponents>

</ItemGroup>

The following is the default configuration, This default is in effect if you do not include any PipelineComponents elements in your project file.

<ItemGroup>

 <PipelineComponents Include="$(ProjectName).PipelineComponents.dll">

   <LocationPath>..\$(ProjectName).PipelineComponents\bin\$(Configuration)</LocationPath>

 </PipelineComponents>

</ItemGroup>

• Edited by SharadVerma 11 hours 48 minutes ago better

 <ItemGroup>
    <ExternalAssemblies Include="Ionic.Zip.dll">
      <LocationPath>..\$(ProjectName)\</LocationPath>
    </ExternalAssemblies>
    
    <Schemas Include="ZipEncoder.dll">
      <LocationPath>..\$(ProjectName)\bin\$(Configuration)</LocationPath>
    </Schemas>
  </ItemGroup>

For you .net component can you try this;

The Components ItemGroup is appropriate for any assembly that contains custom .NET components (classes).  The assembly must contain only .NET artifacts.

<ItemGroup>

 <Components Include="MyComponents.dll">

   <LocationPath>..\$(ProjectName).Components\bin\$(Configuration)</LocationPath>

 </Components>

</ItemGroup>

Include attribute: DLL file name

The error you are facing is mainly related to visual studio not BTDF one, from the project properties I renamed your DLL name same as your project name and when I try to build it is never throwing the error you are facing.

Rest of the corrections for your BTDF file send you on email.

Regards,

Sharad

can you rebuild, build the complete solution ?

are all 3 dll's being GAC'ed ?

I did not receive any email  b

Now I am getting new error

Object reference not set to an instance of an object ?

I closed complete Visual Studio and opened the solution again, receiving following error on build

This is correct location for ZipEncoder.dll can you please verify this??

It is not taking this path. Try loading it from the same folder from which you are loading and able to GAC Ionic.zip Dll.

Regards,

Sharad

• Edited by SharadVerma Monday, July 20, 2015 7:03 PM better

This is correct location for ZipEncoder.dll can you please verify this??

It is not taking this path. Try loading it from the same folder from which you are loading and able to GAC Ionic.zip Dll.

Regards,

Sharad

• Edited by SharadVerma Monday, July 20, 2015 7:03 PM better

Are you sure you are following this steps carefully

1. Set the IncludePipelineComponents property to true

The property may be included in any PropertyGroup, but is commonly placed in the first PropertyGroup in the project file.

<PropertyGroup>

 ...

 <IncludePipelineComponents>true</IncludePipelineComponents>

 ...

</PropertyGroup>

2. Add a PipelineComponents ItemGroup

<ItemGroup>

 <PipelineComponents Include="$(ProjectName).PipelineComponents.dll">

   <LocationPath>..\PipelineComponents\bin\$(Configuration)</LocationPath>

 </PipelineComponents>

</ItemGroup>

The following is the default configuration, This default is in effect if you do not include any PipelineComponents elements in your project file.

<ItemGroup>

 <PipelineComponents Include="$(ProjectName).PipelineComponents.dll">

   <LocationPath>..\$(ProjectName).PipelineComponents\bin\$(Configuration)</LocationPath>

 </PipelineComponents>

</ItemGroup>

• Edited by SharadVerma Monday, July 20, 2015 7:16 PM better

Are you sure you are following this steps carefully

1. Set the IncludePipelineComponents property to true

The property may be included in any PropertyGroup, but is commonly placed in the first PropertyGroup in the project file.

<PropertyGroup>

 ...

 <IncludePipelineComponents>true</IncludePipelineComponents>

 ...

</PropertyGroup>

2. Add a PipelineComponents ItemGroup

<ItemGroup>

 <PipelineComponents Include="$(ProjectName).PipelineComponents.dll">

   <LocationPath>..\PipelineComponents\bin\$(Configuration)</LocationPath>

 </PipelineComponents>

</ItemGroup>

The following is the default configuration, This default is in effect if you do not include any PipelineComponents elements in your project file.

<ItemGroup>

 <PipelineComponents Include="$(ProjectName).PipelineComponents.dll">

   <LocationPath>..\$(ProjectName).PipelineComponents\bin\$(Configuration)</LocationPath>

 </PipelineComponents>

</ItemGroup>

• Edited by SharadVerma Monday, July 20, 2015 7:16 PM better

Hi ,

Please confirm ZipEncoder is external assembly or schema dll .?

If your BTDF code you have incuded ZipEncoder as schema assembly,.

It should be like below

<ItemGroup>
    <ExternalAssemblies Include="Ionic.Zip.dll">
      <LocationPath>..\$(ProjectName)\</LocationPath>
    </ExternalAssemblies>
    
   <ExternalAssemblies Include="ZipEncoder.dll">
      <LocationPath>..\$(ProjectName)\bin\$(Configuration)</LocationPath>
    </ExternalAssemblies>
  </ItemGroup>

Also verify the relative path and it should point to correct folder location where assembly exists .

Thanks

Abhishek

I see that for some reason the code is getting locked in my VS2013. I can build the project, but when I rebuild it is saying : Unable to delete file '...\ZipEncoder.dll '. Access to the path 'C:\...\bin\Debug\ZipEncoder.dll' is denied.

How can I fix this ?