CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums
Results 1 to 2 of 2
  1. #1
    Join Date
    Dec 2005

    [RESOLVED] WinForms code generation

    There are a few things that I don't like about the code that is generated for WinForms:

    a) Each member is preceded by the access specifier, instead I would like to have blocks.

    b) In InitializeComponent is a this-> in front of all calls/assignments, if the this-> is beeing removed the code still compiles but the designer doesn't work any longer.

    c) All code is beeing generated in the header, I only would like to have the declarations in the header.

    d) Several System namespaces are already visible (using namespace System::*), so what is the point of having System::Windows::Forms:: in front of all member declarations?

    e) System::Void can be substituted with void, which is more natural.

    I would like to have clean, human readable code.
    Last edited by ABuenger; June 22nd, 2006 at 05:32 PM.

  2. #2
    Join Date
    May 2006

    Re: WinForms code generation

    Totally agree with you on all points. You actually captured them all pretty nicely

    The problem we have is that this code is both generated and later parsed by the CodeDOM parser which is a very primitive code parser / generator. Revamping that parser is quite an undertaking. Part of the large architectural changes we're currently planning (which were mentioned in other posts) will eventually phase out these very rudimentary parsers.

    The bottom line is, you will not see this get better in Orcas; but we're working on the root cause of the problem.

    Tarek Madkour
    Lead Program Manager
    Microsoft Visual C++
    Tarek Madkour
    Lead Program Manager
    Microsoft Visual C++

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Click Here to Expand Forum to Full Width