Fishery

The CAS mechanism in .NET allows for tighter control over code usage of resources by the user of a particular machine. For example, let’s say I bought a component object model (COM) server from a component vendor that has one coclass called CCompletelySafe that implements the IItsOK interface. This interface has one method called NothingBadWillHappen(). To get this to run, I add the reference to my VB application, and start coding away, like so:

Dim oOK As IItsOK
Set oOK = CreateObject(”TrustMe.CCompletelySafe”)
oOK.NothingBadWillHappen()

Unfortunately, in no time at all I’ve e-mailed everyone in the company a bunch of links that will probably get me fired. Plus, my files are being deleted at a furious rate, and my computer is also creating a bunch of HTTP traffic. The real problem here is that I can’t determine what that method call will do until I invoke it.