Assembly repository using an IL disassembler instead of System.Reflection - SyntaxEditor .NET Languages Add-on for WPF Forum

Posted 12 years ago by Nicolas

I see many (and critical) problems about using SyntaxEditor in a complex (but real !) context : many ProjectAssembly targeting different .Net framework versions (like a VisualStudio solution). For exemple, ProjectA targeting .Net 2.0 and ProjectB referencing ProjectA and targeting .Net 4.0

The default assembly repository implementation (FileBasedAssemblyRepository) use System.Reflection and can't reflect multiple version of same assembly.

Using a disassembler (like Mono.Cecil) solve the problem. This article, explain the benefits of using Mono.Cecil vs System.Reflection : http://codebetter.com/patricksmacchia/2008/03/18/mono-cecil-vs-system-reflection/.

Will actipro going to implement this kind of solution (just a IBinaryAssembly implementation based on Mono.Cecil.AssemblyDefinition) ?

According to me, it's the main obstacle to use SyntaxEditor to build a real .Net productivity tool.

Comments (1)

Posted 12 years ago by Actipro Software Support - Cleveland, OH, USA

Hi Nicolas,

Thanks for the suggestion. We can possibly look into this in the future. We can't use it by default since many large corporate customers have us sign a waiver that the product doesn't rely on open source code. So if we did have an implementation of it, it would need to be in a separate assembly that came along with the add-on, usable as an option.

We agree, Cecil is much nicer than System.Reflection and solves many issues that reflection has.

Actipro Software Support

The latest build of this product (v24.1.4) was released 1 month ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.