WPF XBAP Growing Pains

Question

I have a browser based application that uses JavaScript and ActiveX for document scanning.  I wanted to free myself of the ActiveX requirements so I set about converting the application to WPF XAML so I could still deploy it remotely. 
After much work I've run across a few problems that have me stumped. 
1.  The Page object Loaded event doesn't fire when run from clickonce deployment in I.E.  It fires when debugging in VS using the presentationhost process.  The app is full trust and I put message boxes at the start of the Load and initialized
events but I get nothing.
2.  How do I remove event handlers for components that have gone out of scope?  As I build the component I attach an event handler so that I can notify each active component that the application state has changed which will change the components
behavior.  However if the component go out of scope the main pages event handler list will still have a reference to it and as I understand it it won't be garbage collected.  I thought about creating another event for the components to fire
when they go out of scope but that doesn't feel right to me.
Kenney

Answer 1

I figured out my problem.  It was insidious.  This is a scanning application that uses twain for interfacing to the scanner devices.  To reduce the dependencies I compiled the data source manager code as managed code into the assembly. 
I got no warning or application errors until I build a test application to load the assembly.  While debugging I got a message about the application attempting to called managed code from the LoaderLock.  I searched and found that code in DLLMain
attempting to access a class I had compiled as a managed type.  I commented out DLLMain and all is well again.
Kenney