VB.NET to VC++

[joe_pool_is]

Am I missing something?

 

I started programming in VB.NET a few years back. Drop a TextBox onto a form, changed its name from Textbox1 to "txtName", then collect this textbox's value during runtime by reading "txtName.Text".

 

Last year, I started working with Borland Builder 6.0. A few things changed when converting to Builder/C++: Now I dropped a TEdit module onto a form, changed its name to "Name", and collected the runtime information using "Name->Text". Their are other features that get a lot more involved with programming than VB.NET does, but that is to be expected. Borland's VCL is impressive!

 

Now I am starting to work my way into VC++, and I was expecting Microsoft to take a good idea (Borland Builder) and expand on it. What I am finding is terrible: I drop an Edit Control onto a form, rename its ID to "IDC_NAME", then attach a CString "m_strMessage" variable to the form by right-clicking it and using a visual attachment tool (?). To get or set information from this Edit Control, I have to first call an UpdateData() function, then read or write to my "m_strMessage" before calling the UpdateData() function again.

 

Is Microsoft's VC++ Team on crack? I am using the "SAMS Teach Yourself Visual C++ .NET in 21 Days", and I am on Day 6. So far, each of the examples in the chapters have started with a new MFC Application Wizard, but making the example work includes an unbelievable number of detailed steps. Why has Microsoft put together a programming language that is so difficult and counter-intuitive as compared to their other products? Granted, I can still create a blank C++ program that works great, but once I open up a new MFC Application Wizard and start programming, simplicity is lost! I can not even tell you where my "m_strMessage" variable exists in the project! Modifying its data type from CString to BOOL or adding another variable programatically seems impossible.

[Machaira]

You have to consider the fact that MFC is ancient in industry time. I never did like MFC. It seemed more convoluted and difficult than necessary. What I don't understand is why a book on .NET programming would be having you make MFC apps? That's just silly. Try creating a Windows Form Application project in C++ instead.

[joe_pool_is]

VC++ book recommendations?

 

What I don't understand is why a book on .NET programming would be having you make MFC apps? That's just silly. Try creating a Windows Form Application project in C++ instead.

This brings up another question: Could anyone recommend a good book for learning modern techniques in Visual C++ .NET? The Teach Yourself in 21-Days book that I am using lists "First Printing: December 2001" below the 2nd Edition title that simply says "Copyright @ 2002 by Sams Publishing."