Is this the right place to curse the non-class wizard in VS.NET?
-
Visual Studio 6 had the wonderful Class Wizard. It was reasonably well designed and I could very easily deal with data members and messages. Some moron at Microsoft got rid of this and replaced it with a nightmarish, convoluted design that requires too many clicks. I fail to see the reasoning behind getting rid of all the nice, productive enhancing features of VC++. (Okay, I do see it; some marketing dweeb ignored the fact that most applications are written in C++ [per Microsoft's own studies] and insisted that VB be the dominant factor in the design of VS.NET. Ultimately, to accomodate C#, they hamstrung the entire IDE, I suppose so the developers wouldn't know what they were missing. I call upon the Visual C++ team at Microsoft to rise up and overthrow the yoke of oppression from the .NET marketing dweebs!) Added two minutes later: Suddenly a loud scream erupts. I try to delete a data member from the class view, BUT I CAN'T :mad: And there's no intuitive way do to so. Aaaagggghhh :mad:
-
Visual Studio 6 had the wonderful Class Wizard. It was reasonably well designed and I could very easily deal with data members and messages. Some moron at Microsoft got rid of this and replaced it with a nightmarish, convoluted design that requires too many clicks. I fail to see the reasoning behind getting rid of all the nice, productive enhancing features of VC++. (Okay, I do see it; some marketing dweeb ignored the fact that most applications are written in C++ [per Microsoft's own studies] and insisted that VB be the dominant factor in the design of VS.NET. Ultimately, to accomodate C#, they hamstrung the entire IDE, I suppose so the developers wouldn't know what they were missing. I call upon the Visual C++ team at Microsoft to rise up and overthrow the yoke of oppression from the .NET marketing dweebs!) Added two minutes later: Suddenly a loud scream erupts. I try to delete a data member from the class view, BUT I CAN'T :mad: And there's no intuitive way do to so. Aaaagggghhh :mad:
Joe Woodbury wrote: Is this the right place to curse the non-class wizard in VS.NET? http://www.codeproject.com/script/comments/forums.asp?forumid=3831[^] :) Jon Sagara Help me out here, Spock. I don't speak stupid.
-
Visual Studio 6 had the wonderful Class Wizard. It was reasonably well designed and I could very easily deal with data members and messages. Some moron at Microsoft got rid of this and replaced it with a nightmarish, convoluted design that requires too many clicks. I fail to see the reasoning behind getting rid of all the nice, productive enhancing features of VC++. (Okay, I do see it; some marketing dweeb ignored the fact that most applications are written in C++ [per Microsoft's own studies] and insisted that VB be the dominant factor in the design of VS.NET. Ultimately, to accomodate C#, they hamstrung the entire IDE, I suppose so the developers wouldn't know what they were missing. I call upon the Visual C++ team at Microsoft to rise up and overthrow the yoke of oppression from the .NET marketing dweebs!) Added two minutes later: Suddenly a loud scream erupts. I try to delete a data member from the class view, BUT I CAN'T :mad: And there's no intuitive way do to so. Aaaagggghhh :mad:
-
I initialy missed the class wizard, but after figuring out the new way of doing things really like it, and find it more intuitive. I'm heading for a spaking aren't I?:-D Should I use 'spanking' in the lounge.;P
Serious questions: How do you delete member variables like the VC6 class wizard did? How do you view a list of the control IDs of a dialog and what member variables and messages have been associated with them? (I'm pretending this is cross posted and ended up in this thread on accident:))
-
Serious questions: How do you delete member variables like the VC6 class wizard did? How do you view a list of the control IDs of a dialog and what member variables and messages have been associated with them? (I'm pretending this is cross posted and ended up in this thread on accident:))
There are no control ID's. Everything is instantiated with member variable names. There are no messages. Things are handled by delegates and events. Expand the "hidden" section in your form.cs file to see the code behind the scenes that VS.NET generates. You'll probably scream again, as I did. But, BTW, that's how you can delete a member variable. On the other hand, I love the fact that there's no more G.D. resource file. Everything is unified by runtime construction. Events are great. I couldn't stand the message, reflected message, etc., architecture of MFC. The property pages are a pain in the butt from a usability point of view, but they are also extensible so you can have custom controls with properties that the next programmer can set right in the designer. It's a love/hate relationship. I wish I had a really large project to implement to really test out the capabilities of C# (preferably one that I got paid for, so I could play on the other person's dime!) Marc
-
There are no control ID's. Everything is instantiated with member variable names. There are no messages. Things are handled by delegates and events. Expand the "hidden" section in your form.cs file to see the code behind the scenes that VS.NET generates. You'll probably scream again, as I did. But, BTW, that's how you can delete a member variable. On the other hand, I love the fact that there's no more G.D. resource file. Everything is unified by runtime construction. Events are great. I couldn't stand the message, reflected message, etc., architecture of MFC. The property pages are a pain in the butt from a usability point of view, but they are also extensible so you can have custom controls with properties that the next programmer can set right in the designer. It's a love/hate relationship. I wish I had a really large project to implement to really test out the capabilities of C# (preferably one that I got paid for, so I could play on the other person's dime!) Marc
I thought he said he was working with C++, not in C#... My latest articles: XOR tricks for RAID data protection Win32 process suspend/resume tool
-
There are no control ID's. Everything is instantiated with member variable names. There are no messages. Things are handled by delegates and events. Expand the "hidden" section in your form.cs file to see the code behind the scenes that VS.NET generates. You'll probably scream again, as I did. But, BTW, that's how you can delete a member variable. On the other hand, I love the fact that there's no more G.D. resource file. Everything is unified by runtime construction. Events are great. I couldn't stand the message, reflected message, etc., architecture of MFC. The property pages are a pain in the butt from a usability point of view, but they are also extensible so you can have custom controls with properties that the next programmer can set right in the designer. It's a love/hate relationship. I wish I had a really large project to implement to really test out the capabilities of C# (preferably one that I got paid for, so I could play on the other person's dime!) Marc
-
Marc, I don't think Joe is asking about C#, he's asking how to do this when developing a C++ program.
I thought that was fairly clear. And for the record, I like the way MFC does messaging, dialogs and windows and dislike how C# does forms.
-
I thought that was fairly clear. And for the record, I like the way MFC does messaging, dialogs and windows and dislike how C# does forms.
Joe Woodbury wrote: And for the record, I like the way MFC does messaging, dialogs and windows and dislike how C# does forms I wholeheartedly agree. Any of you C++ guys out there switching to C# can stop bitching about VB because you are now programming in it. :rolleyes: This is coming from a guy who cut his teeth on VB (but don't be too quick to label me, I was using Hardcore VB and fists full of API to do all the things VB couldn't). Man, was I suprised when I got into C++ and saw how easy it was to accomplish things that VB made difficult. :laugh: The C++ dialog editor could have used a facelift, and WinForms anchoring is cool, but the way WinForms is wired together just makes me queezy. -- If it starts to make sense, you're in a cult.
-
Serious questions: How do you delete member variables like the VC6 class wizard did? How do you view a list of the control IDs of a dialog and what member variables and messages have been associated with them? (I'm pretending this is cross posted and ended up in this thread on accident:))
Joe Woodbury wrote: How do you view a list of the control IDs of a dialog and what member variables and messages have been associated with them? Open the .RC file in the source editor and look and the raw code. :eek: Compare to the MESSAGE_MAP and DoDataExchange in the .CPP file :omg: Joe Woodbury wrote: How do you delete member variables like the VC6 class wizard did? Delete them from the .H file and fix compile errors. :wtf: And of course, pretend this :(( is the Indian from the old littering PSAs on TV 'cause what I said above is really sad. -- If it starts to make sense, you're in a cult.
-
Joe Woodbury wrote: How do you view a list of the control IDs of a dialog and what member variables and messages have been associated with them? Open the .RC file in the source editor and look and the raw code. :eek: Compare to the MESSAGE_MAP and DoDataExchange in the .CPP file :omg: Joe Woodbury wrote: How do you delete member variables like the VC6 class wizard did? Delete them from the .H file and fix compile errors. :wtf: And of course, pretend this :(( is the Indian from the old littering PSAs on TV 'cause what I said above is really sad. -- If it starts to make sense, you're in a cult.
This is what Tom posted: Joe Woodbury wrote: How do you view a list of the control IDs of a dialog and what member variables and messages have been associated with them? Open the .RC file in the source editor and look and the raw code. Compare to the MESSAGE_MAP and DoDataExchange in the .CPP file Joe Woodbury wrote: How do you delete member variables like the VC6 class wizard did? Delete them from the .H file and fix compile errors. And of course, pretend this :(( is the Indian from the old littering PSAs on TV 'cause what I said above is really sad. * * * This is what came in my email: Joe Woodbury wrote: How do you view a list of the control IDs of a dialog and what member variables and messages have been associated with them? Delete them from the .H file and fix compile errors. :wtf: Joe Woodbury wrote: How do you delete member variables like the VC6 class wizard did? Open the .RC file in the source editor and look and the raw code. [eek] And of course, pretend this :(( is the Indian from the old littering PSAs on TV 'cause what I said above is really sad. * * * Note that the "Delete them..." and "Open the .RC file..." paragraphs are swapped! Tom, did you edit your message?
-
This is what Tom posted: Joe Woodbury wrote: How do you view a list of the control IDs of a dialog and what member variables and messages have been associated with them? Open the .RC file in the source editor and look and the raw code. Compare to the MESSAGE_MAP and DoDataExchange in the .CPP file Joe Woodbury wrote: How do you delete member variables like the VC6 class wizard did? Delete them from the .H file and fix compile errors. And of course, pretend this :(( is the Indian from the old littering PSAs on TV 'cause what I said above is really sad. * * * This is what came in my email: Joe Woodbury wrote: How do you view a list of the control IDs of a dialog and what member variables and messages have been associated with them? Delete them from the .H file and fix compile errors. :wtf: Joe Woodbury wrote: How do you delete member variables like the VC6 class wizard did? Open the .RC file in the source editor and look and the raw code. [eek] And of course, pretend this :(( is the Indian from the old littering PSAs on TV 'cause what I said above is really sad. * * * Note that the "Delete them..." and "Open the .RC file..." paragraphs are swapped! Tom, did you edit your message?
-
I was so overwhelmed with creating my response that I initially sent it all backwards and lacking in detail. I quickly edited my reply. Sorry. :~ -- If it starts to make sense, you're in a cult.
That's what I figured, but wondered if there was a bug. Not that it mattered, in the sense that there is no nice solution, the answers are interchangeable:((
-
Serious questions: How do you delete member variables like the VC6 class wizard did? How do you view a list of the control IDs of a dialog and what member variables and messages have been associated with them? (I'm pretending this is cross posted and ended up in this thread on accident:))
Joe Woodbury wrote: How do you delete member variables like the VC6 class wizard did? Hmmm, a good design doesnt require to delete a memeber variable :cool: Seriously, go to the header file and remove it manually seems to be the only way :~ Joe Woodbury wrote: How do you view a list of the control IDs of a dialog and what member variables and messages have been associated with them? Select the class in class view, r-click -> properties and then click on the events button in the properties. Last words: Take a look at the "Where Are ClassWizard and WizardBar in Visual C++ .NET?" topic in the help files - the truth is out there :-D
-
I thought that was fairly clear. And for the record, I like the way MFC does messaging, dialogs and windows and dislike how C# does forms.
Oops. I got confused with the reference to "accomodating C#". Sorry! Marc