Windows Forms decompile but designer gives errors

4 posts, 0 answers
  1. Martin
    Martin avatar
    1 posts
    Member since:
    Jan 2014

    Posted 09 May 2016 Link to this post

    I decompiled a VB.NET application built around 2011.

    The decompiled code looks fine - no errors when I load it into VS 2015.

    However, when I attempt to open a form designer I get many errors.

    Basically two types:

    The type 'System.Windows.Forms.Form' had no property named 'XXXX' where XXXX is a control name like txtText1.

    Duplicate Declaration of member 'point' (same for 'size')

    1. How can I fix this?

    2. IS there a step-by-step guide to decompiling windows forms and getting them to work in VS agiain?

    Screenshots attached.



  2. Alexander
    Alexander avatar
    336 posts

    Posted 10 May 2016 Link to this post

    Hi Martin,

    1. These problems can be fixed manually. However, this should not be needed and it's obviously a bug.
    2. No, there is not such tutorial. Basically, it should be enough to generate project using JustDecompile, open it in Visual Studio and hit "Run".

    Would it be possible, that you zip the application, where that happens, and send it over to my email - alexander.dimitrov [at] Rather unfortunately, this seems to be the only way to reproduce these problems. Please, note that [at] must be replaced with @.

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  3. Jamie
    Jamie avatar
    5 posts
    Member since:
    May 2017

    Posted 06 May 2017 in reply to Alexander Link to this post

    Hi Alexander

    Found your this thread / your response after searching for solutions to the problem I was having - I've recently decompiled a WindowsForms application using Telerik, and the Windows Forms designer file is giving many errors of the type 'System.Windows.Forms.Form' had no property named 'XXXX' where XXXX is a control name like 'StatusStrip1'.

    Is this a bug in JustDecompile? Is there a way for me to manually fix these errors since your reply last May?  


  4. Travis
    Travis avatar
    13 posts
    Member since:
    Jul 2014

    Posted 01 Feb Link to this post

    I'm having similar issues, anyone have any luck with resolving these issues??
Back to Top