Bill Blogs in C#

I recently got a question that had a lot to do with the order that events are processed in an ASP.NET page. There was an article on this topic on 15 seconds that covered the topic rather well.

This is just fantastic news.  I (and many others) have been asking for this feature since VS.NET 1.0. 

Thanks to all involved for all the work:

Our area .NET User group, GANG, is working with Microsoft to host the .NET To Go Mobility Roadshow on Wed., Oct 20, 2004 at the Microsoft Offices in Southfield.

From the meeting announcement: 

"The .NET To Go Mobility Roadshow will provide you with the answers to your mobile development questions. Digging into the details, using more code and fewer slides, these technical sessions will show you how to develop and implement mobile solutions using the .NET Compact Framework and languages you are already familiar with. To register for this FREE event or to learn more, go to www.msmobilitytour.com. "

Registration is required to make sure that you can get in. You can register at the MS Events page - http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032259728&Culture=en-US.

Well, registration is not absolutely required, but it is strongly recommended.  If the room is full, you'll get in only if you have registered.

Question:

Is MFC considered to be obsolete technology? If so, what has replaced it? .NET?

Answer:

It depends on what you are doing, and exactly what part of MFC you mean.

MS has clearly placed an emphasis on .NET and Windows Forms as the best toolkit for much of what MFC had been used. In that sense, I would not do any Windows UI development based on the MFC libraries now.

But, that is not the same as saying that C++ is deprecated. The C++ compiler is being enhanced in Visual Studio 2005, including better support for managed code and .NET Windows Forms.  There are some enhancements that relate to the C++ Standard Library as well. In fact, the C++ compiler is probably closer to the C++ standard than many other commercial compilers these days.

I’m seeing more C# (and VB.NET) development than native C++, but I know there is a tremendous amount of C++ code in production being actively maintained and extended. My own preference is to create a plan to migrate native C++ code to .NET based code over a few releases. The final destination would be C#, using managed C++ as the interim step.

So, the bottom line (at least for me) is that I would avoid using the MFC libraries in new development. I would prefer using the standard C++ library (for C++ development) and the .NET BCL for everything else.