none
Deleted RRS feed

All replies

  • To debug the last build of a pipeline component, you need:

    1. Copy the output to <BizTalk Installation Path>/Pipeline Components
    2. Update in the GAC the DLL 
    3. Restart the associated Host Instance
    4. Attach to the associated Host Instance process

    Tuesday, April 3, 2018 3:50 PM
  • Are you still sure you don't want help explaining why an Orchestration is the best solution?

    Or is this for something different?  If so, can you list the exact steps you're trying?


    Tuesday, April 3, 2018 6:23 PM
    Moderator
  • First thing, how you have developed your custom pipeline component.

    First thing you don’t need to GAC your pipeline DLL.

    Please refer this link.https://docs.microsoft.com/en-us/biztalk/core/deploying-pipeline-components.

    Rebuild your project into DEBUG mode copy dll and PDB into (<installation directory>\Pipeline Components folder).

    Restart the host and attached the BizTalk process to solution and try again.

    Thanks,

    Chandra

    Tuesday, April 3, 2018 7:15 PM
  • Deleted
    Tuesday, April 3, 2018 7:26 PM
  • HOLD ON!

    Do not put the component Assembly in the %Pipeline Components% folder.

    Follow these instructions to build and deploy the assembly: BizTalk Server: Deploying Custom Pipeline Components in BizTalk Server 2006 and Higher

    Wrapper?  You probably don't need a pipeline component to create a wrapper.  Can you explain what you're trying to accomplish?

    It's not very clear, do you have the source code?


    Tuesday, April 3, 2018 7:38 PM
    Moderator
  • Deleted
    Tuesday, April 3, 2018 7:41 PM
  • Or is this for something different?  If so, can you list the exact steps you're trying?


    Tuesday, April 3, 2018 8:12 PM
    Moderator