|
Home > Archive > BizTalk Server Framework > February 2006 > Properties in receive pipeline component
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Properties in receive pipeline component
|
|
|
| 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 2006-02-03, 5:53 pm |
| 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
> 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
| |
|
| 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.
"Jon Flanders" wrote:
> 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
>
>
>
>
|
|
|
|
|