reflectoraddins Work Item Rss Feed

Created Issue: PowerShell add-in reports "Unsupported statement TryCatchFinallyStatement" [16447]

VictorWoo — Wed, 24 Aug 2011 07:11:57 GMT

PowerShell add-in reports "Unsupported statement TryCatchFinallyStatement"
Doesn't powershell add-in support try..catch..finally statement?

Closed Issue: Plugins not compatible with Reflector 7 [15221]

Musmuris — Thu, 30 Jun 2011 10:02:58 GMT

The current version of the plugins are not compatible with the new Reflector 7 (beta)
Comments:

Add-ins have been recompiled against Version 7 now

Commented Issue: Plugins not compatible with Reflector 7 [15221]

sailro — Wed, 16 Mar 2011 16:27:55 GMT

The current version of the plugins are not compatible with the new Reflector 7 (beta)
Comments: ** Comment from web user: sailro **

Reflector 7 has changed its assembly version (previously 5.0.0.0, now 7.0.0.0), so that lots of plugins fail to load, but without any plugin API changes.
Here is a simple tool to patch all references to Reflector assembly with custom version, so you don't need to get the plugin source code and recompile.

Tested with Reflexil 1.1, BamlViewer, Graph, CppCli.

http://bit.ly/eTPL3D

Commented Issue: Plugins not compatible with Reflector 7 [15221]

richarddeeming — Tue, 15 Mar 2011 15:53:11 GMT

The current version of the plugins are not compatible with the new Reflector 7 (beta)
Comments: ** Comment from web user: richarddeeming **

Most of the add-ins still work; they just need to be re-compiled.

1. Download the latest source code [1];
2. Copy Reflector.exe into the "Build" directory;
3. Open the project in Visual Studio;
4. Use the configuration manager to change the platform from ".NET 1.0" to "Any CPU";
5. Change the target framework to .NET 3.5;
6. Recompile the add-ins;

You'll need to add a reference to System.Xml to the VulcanLanguage project. All of the other projects will compile without changes.

Step 5 is needed because Reflector is now using WPF, which isn't available from a .NET 2.0 project.

[1] http://reflectoraddins.codeplex.com/SourceControl/list/changesets

Created Issue: Plugins not compatible with Reflector 7 [15221]

JohaViss — Wed, 02 Feb 2011 08:49:04 GMT

The current version of the plugins are not compatible with the new Reflector 7 (beta)

Created Issue: BamlViewer does not recognize BasedOn correctly [14560]

GeertvanHorrik — Thu, 28 Oct 2010 12:17:40 GMT

I always uses the first one that is found for all styles that are based on a specific type. This is because the reader.ReadInt16() for the staticResourceIdentifier inside the ReadPropertyWithStaticResourceIdentifier method always returns 0.

Commented Issue: BamlParser does not correctly handle attached properties with namespace prefix (?) [11918]

OzgurDunyam — Sat, 24 Jul 2010 19:37:10 GMT

I have an element in my XAML with an attached property defined in my own code:

<SomeElement l:Attached.Property="foo"/>

The namespace prefix "l" is of course mapped to the .NET namespace where the attached property is defined.

When i try to parse the BAML stored in the assembly resource (using BamlTranslator), the result is

<SomeElement Property="foo"/>

that is, the namespace prefix and the part on the left-hand side of the dot is missing.
Comments: ** Comment from web user: OzgurDunyam **

<a title='Sesli Sohbet' href='http://www.ozgurdunyam.com'>Sesli Sohbet</a>

Commented Issue: BamlParser does not correctly handle attached properties with namespace prefix (?) [11918]

sisnaz — Thu, 22 Apr 2010 18:04:33 GMT

Yeah, the Baml Viewer is jacked for the 3.5 and 4.0 framework. It doesn't appear to have been updated for a few years now. It does ok for the most part, but the namespaces are all over the place. The template bindings is another problem I'm finding. It's a great tool, hopefully they will update it soon.

Created Issue: BamlParser does not correctly handle attached properties with namespace prefix (?) [11918]

erikakerfeldt — Wed, 24 Feb 2010 18:55:08 GMT

Created Issue: quite a few download links leads to graph.zip instead of the target file [11877]

gg9 — Mon, 22 Feb 2010 17:59:42 GMT

there seems to be wrong links to download to a number add-Ins

Commented Issue: Reflector.Diff: Always comparing to the self

bemar — Tue, 24 Feb 2009 06:58:43 GMT

I'm trying to compare two versions of the same assembly, both located on a remote share (I'm using a UNC path). I open one assembly in Reflector and use the Browse buttons of the Diff screen and dialog boxes to locate the second assembly which resides in a different folder. When I select the second assembly and click OK, Diff displays "Comparing to self" in the top label and does not show any information about the second assembly. I must mention that both assemblies have the same version, but they are in fact different. I thought that it could be an issue with a UNC path, so I copied the second assembly to my desktop and renamed it, but still got the same result. If I pick a system assembly, Diff works as expected.
Comments: ** Comment from web user: bemar **

Here's my workaround. I recompiled the latest assembly and increment the version number in AssemblyInfo.cs (just to make it different from the old one). Add the two assemblies (old and new version) in Reflector. Select the first assembly then click the Tools->Assembly Diff submenu. There you go.

Created Issue: PowerShell Langauge bug in multiplication

Jaykul — Thu, 16 Oct 2008 14:14:41 GMT

First of all, AWESOME work, thanks to everyone involved ... and ... is this still the best place to post bugs for these?

I have an assembly where the code generated looks like this in C#:

{{
for (int i = 0; i < num5; i++)
{
double num9 = (random.NextDouble() * num6) + num;
...
}
}}

But like this, in PowerShell:

{{
for($i = 0; ($i -lt $num5); $i++)
{
$num9 = (($random.NextDouble()$num6) + $num)
...
}
}}

It's just missing a multiplication operator: *

Created Issue: Reflector auto-update doesn't work through a non-MS proxy server

SSG31415926 — Fri, 25 Jul 2008 17:30:30 GMT

Reflector doesn't allow the user to submit credentials as part of the auto-update process meaning that everytime a new version is released the built-in one is disabled and a new version has to be downloaded manually.

Created Issue: Crash when expanding types from disassembler view

ewest305 — Fri, 18 Jul 2008 12:02:02 GMT

Disassemble System.Linq. From disassembler view, click to expand types then App crash. The Linq assembly is under System.Core. Screenshot of error provided.

Created Issue: Resource Extractor

grigorey — Mon, 16 Jun 2008 08:39:15 GMT

This is .NET Reflector Add-In that allows extraction of the resources form the assembly into provided folder.

To use this:

1) Click on the assembly (root element)

2) Tools --> Extract Resources

3) Choose a folder (via folder browser window)

4) Click OK, all resources from an assembly will be extracted to specified folder.

Enjoy...

PS. I do not take any responsibility for how you will use it nor if any damage is cause to you or machine you executed this add-in on, This is for educational reasons only.

Commented Issue: Reflector.Diff: Always comparing to the self

thoughtcriminal — Wed, 11 Jun 2008 16:53:00 GMT

Another comment here is that although Reflector.Diff is very nice I found it inconvenient for one of 2 typical scenarios:
1) you are looking at a specific place in code (typically a method)
2) you are looking at what changes are in the whole assembly
Re 1) Reflector.Diff works like charm
Re 2) It's much better to export certain assembly using the built-in Reflector export feature which will produce "a project" for you and then you should be able to use any file/directory comparison tool you prefer to use (I recommend open-source WinMerge or built-in comparison tool from Total Commander)

Commented Issue: Reflector.Diff: Always comparing to the self

thoughtcriminal — Wed, 11 Jun 2008 12:48:13 GMT

Ok, I just confirmed that the problem 99,99% is caused by assembly version number.
I used Reflexil addon for .NET Reflector to update the assembly version number. After I saved Reflector.Diff started working as expected. I haven't actually got into the details of it but possibly Reflexil does many changes (besides the version number) to the original assembly so probably you should expect some changes like references order change, etc.

Commented Issue: Reflector.Diff: Always comparing to the self

thoughtcriminal — Wed, 11 Jun 2008 12:32:06 GMT

I get the same result with the practically the same scenario (I'm not loading from UNC, but local hard drive).
Anyone knows how to change the version of assembly?

COMMENTED ISSUE: Add Comment functionality to FileDisassembler

lutzroeder — Thu, 05 Jun 2008 10:00:18 GMT

If you are in Reflector and you go on a special Class, press the space key, you will see the disassembled class WITH COMMENTS (XML comments). If you use the "FileDisassembler" you dont see the comments (e.g. <summary> This is a summary</summary>) any more. Please provide the possibility to create disassambled file WITH comments. Thanks.
Comments: ** Comment from web user: lutzroeder **

Reported to author of FileDisassembler.

** Closed by lutzroeder 9/12/2007 12:36 AM

CREATED ISSUE: Reflector.Diff: Always comparing to the self

alekdavis — Mon, 05 May 2008 19:06:35 GMT