Bypass soap client when implementing a PSI Extension

[kernel]

When implementing a PSI extension can we bypass the soap client and work
directly with the service class? If so what assembly is the service class in?
Also are there any other project server-side api's that you can use when
implementing a PSI extension?

 

[Bryant Likes]

When implementing a PSI extension can we bypass the soap client and work
directly with the service class? If so what assembly is the service class
in?
Also are there any other project server-side api's that you can use when
implementing a PSI extension?

This is something I've been trying to do for some time. Based on what I've
run into so far you can't do this. The reason is because if you look at all
the api code using .NET reflector you will see that everything expects there
to be a custom web context around the call which I was unable to duplicate.

There might be a way around it but I haven't found it and no one has
suggested anything when I've asked the question before.

 

[kernel]

ok. There are ways to mock an http context but this sounds like it may be an
unpredicable solution.