Properties in receive pipeline component

[Chris]

Hello all,

I am having an intermitent issue with promoting a public property in my
receive pipeline component. I have developed a pipeline component that has
one public property that can be configured at design time.

Initially, I was able to drag the new pipeline component to my pipeline
design surface(dissasemble stage), and was able to set the property in the
property page. However, now, when I want to create another pipeline, and use
the pipeline component, I can no longer see the promoted property in the
properties page of the pipeline component after I have dropped it to the
design surface.

Does anyone know if this may be a bug. It is very, very frustrating.

Kindest Regards
Chris

[Jon Flanders]

Chris - my guess is that somehow an old version of your component is being
cached by VS. Try this - close VS.NET - go to a VS.NET command prompt and
run "gacutil /cdl" - this will clear the "download cache" which vs.net
uses to cache certain designer components.


Jon Flanders [MVP]
http://www.masteringbiztalk.com
http://www.quicklearn.com/workflow.htm

Post by Chris
Hello all,
I am having an intermitent issue with promoting a public property in
my receive pipeline component. I have developed a pipeline component
that has one public property that can be configured at design time.
Initially, I was able to drag the new pipeline component to my
pipeline design surface(dissasemble stage), and was able to set the
property in the property page. However, now, when I want to create
another pipeline, and use the pipeline component, I can no longer see
the promoted property in the properties page of the pipeline component
after I have dropped it to the design surface.
Does anyone know if this may be a bug. It is very, very frustrating.
Kindest Regards
Chri

[Chris]

Tried that, and it didn't work. This is really strange. It really seems as
though it is a VS.NET bug of some sort.

Post by Jon Flanders
Chris - my guess is that somehow an old version of your component is being
cached by VS. Try this - close VS.NET - go to a VS.NET command prompt and
run "gacutil /cdl" - this will clear the "download cache" which vs.net
uses to cache certain designer components.
Jon Flanders [MVP]
http://www.masteringbiztalk.com
http://www.quicklearn.com/workflow.htm

Post by Chris
Hello all,
I am having an intermitent issue with promoting a public property in
my receive pipeline component. I have developed a pipeline component
that has one public property that can be configured at design time.
Initially, I was able to drag the new pipeline component to my
pipeline design surface(dissasemble stage), and was able to set the
property in the property page. However, now, when I want to create
another pipeline, and use the pipeline component, I can no longer see
the promoted property in the properties page of the pipeline component
after I have dropped it to the design surface.
Does anyone know if this may be a bug. It is very, very frustrating.
Kindest Regards
Chris

[Lucas R. Vogel]

If you referenced a previous version that didn't have the custom property in
it, then you could have a copy of that sitting somewhere.

I've run into problems where I find myself using 'old' versions of custom
pipeline components. Here's what I suggest:

- checking your 'Pipeline Components' directory and deleting the assembly
out of there

-check the project directory for the custom pipeline component and deleting
any and all assemblies in there

-Open the pipeline component solution, verify your build path settings, and
do a full rebuild.

-Open the pipeline project, remove all references to the assembly in teh
pipeline and in the references, and close the project.

-Go into the pipeline project and remove all assemblies in your project
directory.

-Open your pipeline project, add your pipeline component back into your
references, and make sure you're not doing a 'copy local'. Make sure your
project references has a reference to the Pipeline Components path.

-Re-add your custom component to your pipeline.

I know it's a lot of steps, but in the development process you can end up
with a lot of redundant assembly copies and references without even knowing
it sometimes. Best approach sometimes is to remove all assemblies and their
references, and start over - especially when adding and referencing new
assembly features, and especially with such a highly dependent object as a
custom pipeline component.

Hope this helps!
Lucas
--
===========
Lucas R. Vogel

Post by Chris
Tried that, and it didn't work. This is really strange. It really seems as
though it is a VS.NET bug of some sort.

Post by Jon Flanders
Chris - my guess is that somehow an old version of your component is being
cached by VS. Try this - close VS.NET - go to a VS.NET command prompt and
run "gacutil /cdl" - this will clear the "download cache" which vs.net
uses to cache certain designer components.
Jon Flanders [MVP]
http://www.masteringbiztalk.com
http://www.quicklearn.com/workflow.htm

Post by Chris
Hello all,
I am having an intermitent issue with promoting a public property in
my receive pipeline component. I have developed a pipeline component
that has one public property that can be configured at design time.
Initially, I was able to drag the new pipeline component to my
pipeline design surface(dissasemble stage), and was able to set the
property in the property page. However, now, when I want to create
another pipeline, and use the pipeline component, I can no longer see
the promoted property in the properties page of the pipeline component
after I have dropped it to the design surface.
Does anyone know if this may be a bug. It is very, very frustrating.
Kindest Regards
Chris