BAML Add in - Red Gate forums

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Topics:

baml x9

asked: Mar 15 '11 at 03:09 PM

Seen: 3102 times

Last Updated: Mar 15 '11 at 03:09 PM

Related Questions

BAML Add in

It appears as though the new .Net Reflector version doesn't support the BAML addin...it fails trying to load. Since there is no way to get a older version of .net relector (even for paying customers) I am left with a tool that isn't doing what I need it to. Can someone at redgate explain why Reflector.BamlViewer.dll no longer works with .net reflector?

asked Mar 15 '11 at 03:09 PM whknight 1

(comments are locked)

5 answers:

oldest newest voted first

Alternatively, you can:

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

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.

answered Mar 15 '11 at 03:51 PM

RichardD
215 ● 6 ● 9 ● 24

Alexander Morou Jul 03 '11 at 03:39 PM

This is probably the safest bet. It's less of a hack and more of a manual update method. In building a new version of the library you ensure that it at least compiles and verifies from a compiler standpoint. Whether it runs properly or not depends on how well the code base was maintained to the current object model. This is also assuming redgate hasn't gone and fixed it: http://www.red-gate.com/MessageBoard/viewtopic.php?p=49466#49466

(comments are locked)

Here is the trick to convert all previous plugins to Reflector 7.

Use Reflexil 1.2 to patch assembly Reference to Reflector.exe. I mean don't update Reflector.exe (which will fails as it is protected) but change the plugin entry point references by increasing the version number from 5.0.0.0 to 7.0.0.0

See: i've patched Graph Addin (which only works with v5) to show you:

It's due to the modification of the Reflector assembly version (which was untouched since v5). I think it's safe to do as the plugin object model was not updated.

Important: quit Reflector before trying to re-add the assembly as a plugin (because it can be in 'cache')

Edit: I've updated the BamlViewer plugin for you, you can download it here:

http://hotfile.com/dl/110355170/557486c/Reflector.BamlViewer.v7.zip.html

Regards

Edit: I've made a #Reflector Plugin Converter [http://bit.ly/eTPL3D][1]

[1]: http://bit.ly/eTPL3D "Reflector plugin converter"

answered Mar 15 '11 at 03:21 PM

reflexil
120 ● 5 ● 10 ● 22

(comments are locked)

Thanks to both....I appreciate your help

answered Mar 15 '11 at 04:45 PM

whknight
1 ● 1 ● 2 ● 2

(comments are locked)

I've just put out an EA build of .NET Reflector 7.2 (build 134) that will load and work with all add-ins compiled against .NET Reflector 5.x and later - when I say work, I mean it'll work with the add-ins as well as it ever did, so if there are bugs in them, they'll still be there, etc.

You can get this build from the bottom of the homepage at http://www.reflector.net/.

More details here: http://www.reflector.net/2011/07/supporting-add-ins-across-multiple-versions-of-reflector/.

HTH,

Bart

answered Jul 05 '11 at 03:36 PM