1 Dll, in our libraries... If called from webservice behaves as expected, if called from winform, uses remoting... HUH?

Question

That's Pretty much it.

I took a set of Active Directory classes we'd had in our webservices for years, and seperated & migrated it into our Libraries so I could also use them in a winform app I'm whipping up.

Migration worked fine. Running it via the original webservice, works normally, I can debug into the Classes just fine.

Same exact Dll, in my winform app, when I run it in the debugger, it's being called via remoting, and I can't debug it becuase almost everything on the objects are remote proxies.

What the heck did I do differntely to make it behave like this? None of the other classes behave like this.

Any insight is greatly appreicatied.

Thanks,

Cal-