08-16-04 10:54 PM
Your orchestration is hitting a persistent point where it is trying to
serialize something
that cannot be serialized.
Are you calling a .Net class that is not marked serialized ?
Another common reason for this problem is XmlDocument ?
XmlDocument class is not serializable. I have seen this when you are using
an external
.Net class that has in instance variable of type XmlDocument. This is
commonly done to
create an the Message in an assembly. The work around is to have a static
method return
XmlDocument.
To fix the problem you can either do exactly what the message says i.e. make
you calls with
in an atomic scope or make sure the object you are working with is
Serialiable.
Cheers,
Raj
"Raju" <Raju@discussions.microsoft.com> wrote in message
news:7D95E540-BC5F-46F2-813D-9BF3215DC4A7@microsoft.com...
> The following error is displayed when i try to complie my orhcestration.
> It contains a scope, a variable pointing to a class.
> Transaction type is declared as None for the scope.
>
> a non-serializable object type can only be declared within an atomic
scope
> or service
>
> But the same is successfully getting compiled in some other project.
>
> What does the error means?
[ Post a follow-up to this message ]
|