Need Help Badly - Silverlight Plugin Crashing after deployment

Topics: Bootstrappers & IoC, Framework Services
Feb 21, 2013 at 10:52 PM
So I went to deploy my application updates last night, just in time to meet the deadline, and when I try to run my application remotely boom it blows up. Ditto if I try to run locally on the webserver (2008R2).

I have done a lot of up dates and upgrades of all my 3rd party tools (including .net 45) so I've wasted the day trying all sorts of different things. At the moment if I strip my application down so that it does not use the bootstrapper and just opens my shell view as the rootvisual manually then it works. As soon as I put the bootstrapper in my application.xaml resources then it crashes.

Everything works locally like a charm (Win8). I managed to deploy my WCF project and have all those services working and this should have been a no brainer just deploying the simple web hosting app.

I have f@$#'d with all the setting out the ying yang but I had CM 1.3.1 deployed earlier this month. Since then the only changes for this release on the server are:

1 - install the .net 4.5 framework on win2008 R2
2 - change the IIS pool and server to use the 4.0 version vs. 2.0
3 - re-deploy via vs 2012 instead of vs2010.

I am at a total loss - I can't even see how to attach the debugger remotely to find out what might be off. In Firefox I just get the plugin crash sad face and ie is less happy.

All I get is an event view crash notification:

Faulting application name: plugin-container.exe, version: 19.0.0.4794, time stamp: 0x511ed156
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc00000fd
Fault offset: 0x0f3a884d
Faulting process id: 0x3378
Faulting application start time: 0x01ce108e439eb911
Faulting application path: C:\Program Files (x86)\Mozilla Firefox\plugin-container.exe
Faulting module path: unknown
Report Id: 822c1660-7c81-11e2-be96-1c6f652f8a9f
Faulting package full name:
Faulting package-relative application ID:

or

Faulting application name: IEXPLORE.EXE, version: 10.0.9200.16482, time stamp: 0x50cfc9bf
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc00000fd
Fault offset: 0x164c526c
Faulting process id: 0x2250
Faulting application start time: 0x01ce108cbb7b037a
Faulting application path: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE
Faulting module path: unknown
Report Id: fb052026-7c7f-11e2-be96-1c6f652f8a9f
Faulting package full name:
Faulting package-relative application ID:
Feb 22, 2013 at 4:58 AM
An upgrade to winserver 2012 (while a nice upgrade) didn't help - still crashing.
Feb 22, 2013 at 7:29 AM
I resolved my issues finally by starting with a clean bootstrapper (helloScreens example) and cleaning up my application.xaml.cs and bootstrapper.

I believe my problems were related to multiple attempts at attaching to the application events and the main window.