No, I still have the same problem with the breakpoints not being hit.

I have read different articles about this, some say you attach your
code to BTSNTSVC.EXE and some say you attach it to devenv.exe. Which
one is it?

Another problem if it is the devenv.exe, that process does not show
for the project I want to debug, just other projects I have open at
the same time.

The problems I am having then occur obviously when I attach it to
BTSNTSVC.exe

/A

[ Post a follow-up to this message ]

BTW, your replies are starting a completely new thread ?

- You attach to BTSNTSvc.exe
- Check the CLR Debug option in the attach dialog box
- If you did not get any error, then you successfully attached to it.

To start from the beginning just in case :
- Create/build your pipeline component; make sure you have the "Generate
Debugging Information"=true in the project properties
- Drop in the <BTSDir>\Pipeline Components directory
- Consume the component in a pipeline inside a BTS project
- Deploy the pipeline and feed it a file

Everytime you change your pipeline component, be sure to undeploy the
pipeline project, copy to BTS Pipeline components directory, redeploy. Also
make sure the ports are using the pipeline you built - undeploying or
redeploying will switch it to passthrough pipeline.

There are no other special things that you need to do.

HTH

ravi



"Axel" wrote:

> No, I still have the same problem with the breakpoints not being hit.
>
> I have read different articles about this, some say you attach your
> code to BTSNTSVC.EXE and some say you attach it to devenv.exe. Which
> one is it?
>
> Another problem if it is the devenv.exe, that process does not show
> for the project I want to debug, just other projects I have open at
> the same time.
>
> The problems I am having then occur obviously when I attach it to
> BTSNTSVC.exe
>
> /A
>

[ Post a follow-up to this message ]