Re: [IronPython] Compiling with Pyc for Silverlight

2009-04-21 Thread Michael Foord
Dino Viehland wrote: You're compiling to a DLL and then trying to import (vs compiling to an EXE)? Yes - it's support packages we're trying to compile. I would have thought that compiling an exe for Silverlight was a lost cause... :-) There are two motivations, mainly speeding up import

Re: [IronPython] Compiling with Pyc for Silverlight

2009-04-21 Thread Dino Viehland
Do you have a simple repro XAP you can send me and I'll take a look? I'm not entirely sure I'll know what's going on as CoreCLR isn't the CLR I'm used to debugging but it's not that different :) -Original Message- From: users-boun...@lists.ironpython.com [mailto:users-

Re: [IronPython] Compiling with Pyc for Silverlight

2009-04-21 Thread Michael Foord
Dino Viehland wrote: Do you have a simple repro XAP you can send me and I'll take a look? I'm not entirely sure I'll know what's going on as CoreCLR isn't the CLR I'm used to debugging but it's not that different :) Attached is a xap file. It has a very simple package compiled with Pyc -

Re: [IronPython] Compiling with Pyc for Silverlight

2009-04-21 Thread Dino Viehland
For some reason the re-write didn't work. After the re-write the new binary in ildasm should have a manifest that looks like: .assembly extern mscorlib { .publickeytoken = (B7 7A 5C 56 19 34 E0 89 ) .ver 2:0:5:0 } .assembly extern Microsoft.Scripting { .publickeytoken = (31 BF 38 56 AD

Re: [IronPython] Compiling with Pyc for Silverlight

2009-04-21 Thread Michael Foord
Dino Viehland wrote: For some reason the re-write didn't work. I didn't rewrite that one. :-) After the re-write the new binary in ildasm should have a manifest that looks like: .assembly extern mscorlib { .publickeytoken = (B7 7A 5C 56 19 34 E0 89 ) .ver 2:0:5:0 } .assembly extern