If you are hosting a control in the browser and have given it elevated permissions (we will use FullTrust for this example) you might notice that you are still getting security exceptions when you try to call protected APIs. Here's what is going on...

If you have a control hosted in the browser and you try to strong name it, you may find that it stops working. Looking at the IEHostLog ( http://blogs.msdn.com/andrewdownum/archive/2006/02/10/Using_DebugIEHost.aspx ) you might see something like this...

Controls hosted in the browser can often be difficult to debug. If anything goes wrong with loading the dll or constructing the control instance, you will get nothing but the standard IE "something is wrong" image (the small icon in the top-left with...