I have a custom pipeline component and a pipeline in my solution.  My custom
pipeline component project has a post-build action to copy it (with
overwrite) to the %BiztalkHome%\Pipeline Components directory.   The pipelin
e
project has the custom component in the toolbox and uses it in the pipeline.

The problem is that when I build the custom pipeline component, the
post-build action fails because Dev Studio has a lock on that component
(probably for the toolbox).  Is there a good workaround for this problem?

Thanks,

Don Tian

[ Post a follow-up to this message ]

Please close Visual Studio if it is open and then run the build process.

Thanks!
This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team
--------------------
|>>Thread-Topic: Cannot overwrite custom component in Pipeline Components
directory
|>>thread-index: AcSMeGjOEbGbfn4uTWy4vNQtWm+inw==
|>>X-WBNR-Posting-Host: 65.170.227.50
|>>From: "examnotes" <DonTian@discussions.microsoft.com>
|>>Subject: Cannot overwrite custom component in Pipeline Components
directory
|>>Date: Fri, 27 Aug 2004 13:57:05 -0700
|>>Lines: 12
|>>Message-ID: <D0F3AF24-F948-4360-937E-A80D0F400FE1@microsoft.com>
|>>MIME-Version: 1.0
|>>Content-Type: text/plain;
|>>	charset="Utf-8"
|>>Content-Transfer-Encoding: 7bit
|>>X-Newsreader: Microsoft CDO for Windows 2000
|>>Content-Class: urn:content-classes:message
|>>Importance: normal
|>>Priority: normal
|>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
|>>Newsgroups: microsoft.public.biztalk.general
|>>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
|>>Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
|>>Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.general:19103
|>>X-Tomcat-NG: microsoft.public.biztalk.general
|>>
|>>I have a custom pipeline component and a pipeline in my solution.  My
custom
|>>pipeline component project has a post-build action to copy it (with
|>>overwrite) to the %BiztalkHome%\Pipeline Components directory.   The
pipeline
|>>project has the custom component in the toolbox and uses it in the
pipeline.
|>>
|>>The problem is that when I build the custom pipeline component, the
|>>post-build action fails because Dev Studio has a lock on that component
|>>(probably for the toolbox).  Is there a good workaround for this problem?
|>>
|>>Thanks,
|>>
|>>Don Tian
|>>

[ Post a follow-up to this message ]

Hi Don,

Besides closing Visual Studio, the component will also be locked by any
processes making use of it. If you're using it in an Isolated host, you'll
have to recycle IIS; if you're using it with an In-Process host, you'll have
to restart the BizTalk service running that host.

Regards

Owen

"Don Tian" wrote:

> I have a custom pipeline component and a pipeline in my solution.  My cust
om
> pipeline component project has a post-build action to copy it (with
> overwrite) to the %BiztalkHome%\Pipeline Components directory.   The pipel
ine
> project has the custom component in the toolbox and uses it in the pipelin
e.
>
> The problem is that when I build the custom pipeline component, the
> post-build action fails because Dev Studio has a lock on that component
> (probably for the toolbox).  Is there a good workaround for this problem?
>
> Thanks,
>
> Don Tian

[ Post a follow-up to this message ]

On Fri, 27 Aug 2004 13:57:05 -0700, Don Tian wrote:

> I have a custom pipeline component and a pipeline in my solution.  My cust
om
> pipeline component project has a post-build action to copy it (with
> overwrite) to the %BiztalkHome%\Pipeline Components directory.   The pipel
ine
> project has the custom component in the toolbox and uses it in the pipelin
e.
>
> The problem is that when I build the custom pipeline component, the
> post-build action fails because Dev Studio has a lock on that component
> (probably for the toolbox).  Is there a good workaround for this problem?
>
> Thanks,
>
> Don Tian

Not really, besides killing visual studio, also recycle btsntsvc.exe
service to ensure biztalk has no locks on the file. It's only on rare
occasions that visual studio will really lock the file (unless you have the
component and the pipeline using the component within the same solution
ofcourse).

HTH,

Martijn Hoogendoorn

[ Post a follow-up to this message ]

From my experince, this problem only occurs if you have (or had) the BizTalk
Pipeline Designer open in your VS session. Close all Pipeline Desinger
Windows, restart VS and you should be able to do turnarounds without having
to restart VS until you open a Pipeline Designer window.

I use the following batch a a post-build-action in my pipeline components
projects:

xcopy "$(ProjectDir)$(Outdir)$(TargetFileName)" "C:\Program Files\Microsoft
BizTalk Server 2004\Pipeline Components" /R /Y /F
IF %ERRORLEVEL% EQU 0 GOTO done
net stop "BizTalk Service BizTalk Group : BizTalkServerApplication"
iisreset
xcopy "$(ProjectDir)$(Outdir)$(TargetFileName)" "C:\Program Files\Microsoft
BizTalk Server 2004\Pipeline Components" /R /Y /F
net start "BizTalk Service BizTalk Group : BizTalkServerApplication"
:done



"Don Tian" wrote:

> I have a custom pipeline component and a pipeline in my solution.  My cust
om
> pipeline component project has a post-build action to copy it (with
> overwrite) to the %BiztalkHome%\Pipeline Components directory.   The pipel
ine
> project has the custom component in the toolbox and uses it in the pipelin
e.
>
> The problem is that when I build the custom pipeline component, the
> post-build action fails because Dev Studio has a lock on that component
> (probably for the toolbox).  Is there a good workaround for this problem?
>
> Thanks,
>
> Don Tian

[ Post a follow-up to this message ]