I've been working with using a .NET class to write some supporting logic for
the rules I'm implementing (mostly date comparison methods).  I've added
those .NET class methods to the vocabulary, used them in policies, and
published/deployed the whole thing.

I made a fact creator and my policies work just fine when I run them from
within the Rules Composer.  However, when I try to run the Policies from an
orchestration, they never fire.  This is directly related to the way that I
am (mis)treating the .NET classes in the rules.

How can I get the policies to access the .NET class while executing from the
orchestration .

(All of the pertinant assemblies have been GAC'ed)

PLEASE help on this, I am going a little crazy!

[ Post a follow-up to this message ]

Are you sure you are passing the object into the Policy?  Are all of the
variables configured?

The Fact creator only works from the composer  - not from an orchestration.

--
Jon Flanders
http://www.masteringbiztalk.com/blogs/jon/

"n.s.tho" <craxymofo@community.nospam> wrote in message
news:9E329199-BE92-4B73-8158-B10F7B1D26AC@microsoft.com...
> I've been working with using a .NET class to write some supporting logic
> for
> the rules I'm implementing (mostly date comparison methods).  I've added
> those .NET class methods to the vocabulary, used them in policies, and
> published/deployed the whole thing.
>
> I made a fact creator and my policies work just fine when I run them from
> within the Rules Composer.  However, when I try to run the Policies from
> an
> orchestration, they never fire.  This is directly related to the way that
> I
> am (mis)treating the .NET classes in the rules.
>
> How can I get the policies to access the .NET class while executing from
> the
> orchestration .
>
> (All of the pertinant assemblies have been GAC'ed)
>
> PLEASE help on this, I am going a little crazy!

[ Post a follow-up to this message ]

I actually just solved this issue few minutes ago.  But thank you very much
for the response.

The problem was that the instance that I was passing down had an out of date
assembly reference, it was using a version that did not have all of the
properties so the rules didn't fire.  I'm assuming that it could assert the
required facts, and therefore skipped the rule processing.

my bad.

"Jon Flanders[MVP]" wrote:

> Are you sure you are passing the object into the Policy?  Are all of the
> variables configured?
>
> The Fact creator only works from the composer  - not from an orchestration
.
>
> --
> Jon Flanders
> http://www.masteringbiztalk.com/blogs/jon/
>
> "n.s.tho" <craxymofo@community.nospam> wrote in message
> news:9E329199-BE92-4B73-8158-B10F7B1D26AC@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]