BOb,

>First, not just anyone should have access to your bizobj dll's. It should be on a secure server directory were only various user names can access it.

I don't know about in Shawn's situation, but the reason we double-check whether we have a valid user using the BizObjects is because we have exposed our BizObjects via Web Services, so that they can be freely accessed ... therefore it's a good idea to check that the client using the Web Service is *supposed* to be using the Web Service.

~~Bonnie


>
>Second, I think this is something that you can deal with by strongly naming your assemblies and using code access security. I haven't dug into it to deeply though.
>
>BOb