Please track ILSpy for updated XAML/BAML support

4 posts, 0 answers
  1. Lex
    Lex avatar
    3 posts
    Member since:
    Jul 2014

    Posted 09 Jul 2014 Link to this post

    From exception call stacks, it is obvious that JustDecompile uses the same XAML/BAML code as ILSpy, and therefore experiences the same issues.

    I just fixed #365 https://github.com/icsharpcode/ILSpy/issues/365 and it is part of ILSpy 2.2. Hope JustDecompile can include this fix to avoid such exceptions.

    I am still working on #470, and will try to fix it in the next few weeks.
  2. Tsviatko Yovtchev
    Admin
    Tsviatko Yovtchev avatar
    408 posts

    Posted 10 Jul 2014 Link to this post

    Hi there,

    First of all, thanks for letting us know about this issue.

    Let me just make sure I got you right. So, in Obfuscar you are using ILSpy's BAML decompiler. Someone reported an exception in that one on a given assembly. You tried using JustDecompile on that same assembly and you got same looking exception there, too.

    Is that correct? If so can I get the offending assembly? You can mail it to tsviatko.yovtchev at telerik dot com.

    Regards,
    Tsviatko Yovtchev
    Telerik
     

    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

     
  3. DevCraft banner
  4. Lex
    Lex avatar
    3 posts
    Member since:
    Jul 2014

    Posted 11 Jul 2014 in reply to Tsviatko Yovtchev Link to this post

    Hi,

    You don't need the original assembly (I don't have rights to share that), because a test assembly can be easily constructed as below,

    1. Create a new WPF project in VS.
    2. Add NuGet package "WPFToolkit" and "WPFToolkit.DataVisualization".
    3. Add new UserControl. Its C# code should be similar to https://github.com/lextm/ILSpy/blob/306e7143b79780d8b529f507f417a10372ccb048/ILSpy.BamlDecompiler/Tests/Cases/issue365.xaml.cs
    4. Modify the XAML to https://github.com/lextm/ILSpy/blob/306e7143b79780d8b529f507f417a10372ccb048/ILSpy.BamlDecompiler/Tests/Cases/issue365.xaml
    5. Compile the project and then use JustDecompile to decompile the BAML file for this UserControl and you can see the exception.

    The ColumnSeries tag is the key here to trigger the bug.

  5. Tsviatko Yovtchev
    Admin
    Tsviatko Yovtchev avatar
    408 posts

    Posted 14 Jul 2014 Link to this post

    Hi,

    Thanks for following through. We'll give it a try.

    Regards,
    Tsviatko Yovtchev
    Telerik
     

    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

     
Back to Top