AttributeUsage.AllowMultiple=true yields “supports only valid CLR assemblies” in JustDecompile-2014.3.1021.0

4 posts, 0 answers
  1. binki
    binki avatar
    3 posts
    Member since:
    Aug 2013

    Posted 13 Jan 2015 Link to this post

    Example:

    using ClassLibrary3;
    using System;
     
    [assembly:CustomAssembly("red")]
    [assembly: CustomAssembly("blue")]
     
    namespace ClassLibrary3
    {
        [AttributeUsage(AttributeTargets.Assembly,AllowMultiple = true)]
        public class CustomAssemblyAttribute
            : Attribute
        {
            public string Color { get; private set; }
            public CustomAssemblyAttribute(string color)
            {
                if (color == null)
                    throw new ArgumentNullException(nameof(color));
                Color = color;
            }
        }
    }

    compiled with Visual Studio 2015 Preview (14.0.22310.1 DP).
  2. Tsviatko Yovtchev
    Admin
    Tsviatko Yovtchev avatar
    409 posts

    Posted 14 Jan 2015 Link to this post

    Hello,

    the current official version of JustDecompile does not fully support VS 2015. That will come shortly. Please, stay tuned and update regularly.

    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. binki
    binki avatar
    3 posts
    Member since:
    Aug 2013

    Posted 14 Jan 2015 Link to this post

    I found out that deleting the .pdb file for the assembly results in JustDecompile being willing to read it. I haven’t been able to find code like that posted in my supposed “reproduction case” that causes JustDecompile to fail to read the assembly.

    Sorry for the false report. I just didn’t think of trying to remove the .pdb—or even of trying to download and open the .dll I had uploaded. And, of course, the assembly I uploaded opens fine—when I open it from my Downloads folder which, of course, does not also contain the .pdb.
  5. Tsviatko Yovtchev
    Admin
    Tsviatko Yovtchev avatar
    409 posts

    Posted 16 Jan 2015 Link to this post

    Hello,

    Thanks for letting us know about this.

    The current unreadable .pdb behavior is terribly wrong and will be fixed in our next release.

    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