How can we help you today? How can we help you today?

Silverlight Framework Assemblies

When you create a new list in the Assembly List Management dialog, the first time you open a brand new list Reflector offers to populate it from one of the versions of .NET on the machine.

This always used to offer Silverlight as one of the options. (Slightly annoyingly, each time Silverlight upgraded, you'd need to recreate the list because everything had moved, but at least it was quick to do this, thanks to Silverlight always being on the list.)

Silverlight no longer seems to appear. (I'm running 6.8.1.3)

It's possible to go and add all the Silverlight assemblies by hand, but since you need to do this every time a new update to Silverlight gets pushed out, this is slightly tedious. Any chance we could have the auto-population of Silverlight assemblies back please?
ian
0

Comments

1 comment

Sort by
  • Bart Read
    Hi Ian,


    It looks like the problem is happening because Reflector now runs as a 64-bit app on 64-bit systems and this screws over the Silverlight discovery. We have a fix for this in 7.x which we'll backport into 6.8 and then put out as a 6.8.2 release, which you'll be able to get via Help > Check for Updates in Reflector. It'll probably be a week or two before this fix is available.

    In the meantime, as a workaround, you might try forcing it to run as 32-bit using the CorFlags utility included with the .NET Framework SDK:

    CorFlags.exe reflector.exe /32Bit+ /force

    Output will be something like the following:

    Microsoft (R) .NET Framework CorFlags Conversion Tool. Version 4.0.30319.1
    Copyright (c) Microsoft Corporation. All rights reserved.

    corflags : warning CF011 : The specified file is strong name signed. Using /Force will invalidate the signature of this image and will require the assembly to be resigned.


    Hope that helps.


    Thanks,


    Bart
    Bart Read
    0

Add comment

Please sign in to leave a comment.