Fishery
Catch many information here
Archives
- January 2012
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- April 2009
- March 2009
- February 2009
- January 2009
-
No Comments
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.