Planning to use MFC 7?
-
I would like to know how many developers are planning on using MFC 7 (or are already using it)? Why, why not?
Why not? given the fact that it's a better version of current MFC and has some cool classes on DHTML, imaging, GDI+ etc. CString also got a face lift. Any other thought? // Fazlul
Get RadVC today! Play RAD in VC++ http://www.capitolsoft.com
-
I would like to know how many developers are planning on using MFC 7 (or are already using it)? Why, why not?
I'm definitely planning on using it! Unfortunately some of the classes are not backwards compatible, if you have used undocumented features - but I guess problems like that is what you ask for by doing that :-( I think MFC is a great framework, and will continue to be that for years to come. Christian Skovdal Andersen
-
I would like to know how many developers are planning on using MFC 7 (or are already using it)? Why, why not?
Yes, when I need it :rolleyes: . I use MFC for 2 things: one is ISAPI extensions, and the second is GUI. Whenever I don't need these, I try to avoid MFC. I'm not a big fan of CString. I vote pro drink :beer:
-
I would like to know how many developers are planning on using MFC 7 (or are already using it)? Why, why not?
currently, i see no need (for me) to switch. -c ------------------------------ Smaller Animals Software, Inc. http://www.smalleranimals.com
-
I would like to know how many developers are planning on using MFC 7 (or are already using it)? Why, why not?
-
I would like to know how many developers are planning on using MFC 7 (or are already using it)? Why, why not?
I probably won't. From what I understand, Visual Studio has undergone a complete facelift, and given the deteriorating quality of Microsoft's UIs these days, I'm not at all keen to try that app. I assume MFC 7 requires VC++ 7, of course. Am I wrong on this?
-
I probably won't. From what I understand, Visual Studio has undergone a complete facelift, and given the deteriorating quality of Microsoft's UIs these days, I'm not at all keen to try that app. I assume MFC 7 requires VC++ 7, of course. Am I wrong on this?
> ..given the deteriorating quality of Microsoft's UIs these days.. This sounds interesting. Can you please explain a bit more?
Get RadVC today! Play RAD in VC++ http://www.capitolsoft.com
-
I probably won't. From what I understand, Visual Studio has undergone a complete facelift, and given the deteriorating quality of Microsoft's UIs these days, I'm not at all keen to try that app. I assume MFC 7 requires VC++ 7, of course. Am I wrong on this?
I don't know much about changes in MFC, but Visual Studio .Net is really great. Try it befor you make any conclusions. I vote pro drink :beer:
-
I probably won't. From what I understand, Visual Studio has undergone a complete facelift, and given the deteriorating quality of Microsoft's UIs these days, I'm not at all keen to try that app. I assume MFC 7 requires VC++ 7, of course. Am I wrong on this?
given the deteriorating quality of Microsoft's UIs these days You have to remember that Microsoft's new UI (I mean the OfficeXP/VSXP one) is liked by far more people than it is disliked by, even though you personally may not like it. It is a huge step forward for Microsoft in terms of accessibility, and I find it a hell of allot more responsive than most other UIs. David Wulff dwulff@battleaxesoftware.com
-
Yes, when I need it :rolleyes: . I use MFC for 2 things: one is ISAPI extensions, and the second is GUI. Whenever I don't need these, I try to avoid MFC. I'm not a big fan of CString. I vote pro drink :beer:
You won't have to use MFC for ISAPI extensions in VS.NET. You can use ATL Server's which provide much more flexibilty in design and development. You should look at my tutorial on using ATL Server. It's been given a very significant face lift. Cheers, -Erik ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ My thoughts are my own and reflect on no other.
-
You won't have to use MFC for ISAPI extensions in VS.NET. You can use ATL Server's which provide much more flexibilty in design and development. You should look at my tutorial on using ATL Server. It's been given a very significant face lift. Cheers, -Erik ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ My thoughts are my own and reflect on no other.
I'm afraid I will have to use ISAPI for a while. We have too much code developed to switch to ATL Server at this moment. Anyway, I've read your article. It's nice. :) I vote pro drink :beer:
-
I would like to know how many developers are planning on using MFC 7 (or are already using it)? Why, why not?
We are not using MFC at all here anymore, I'll use it at home with beta 2, just to learn how to. Christian As I learn the innermost secrets of the around me, they reward me in many ways to keep quiet. Men with pierced ears are better prepared for marriage. They've experienced pain and bought Jewellery.
-
I'm afraid I will have to use ISAPI for a while. We have too much code developed to switch to ATL Server at this moment. Anyway, I've read your article. It's nice. :) I vote pro drink :beer:
ATL Server is ISAPI just cleaned up. The resource files(HTML) in your ISAPI extensions are nolonger in the DLL. They are outside, modifyable without recompiling, and with a new extension. And the objects that exist are wrapped up much nicer now into class objects providing much of the features present in the ASP request and response objects. Thus making the over all development time much quicker and simpler. The only dependency is needing the new version of atl3.dll. Just my 2 cents, I can understand that current developments would not be feasible but future developments might benefit from it. Cheers, -Erik ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ My thoughts are my own and reflect on no other.
-
We are not using MFC at all here anymore, I'll use it at home with beta 2, just to learn how to. Christian As I learn the innermost secrets of the around me, they reward me in many ways to keep quiet. Men with pierced ears are better prepared for marriage. They've experienced pain and bought Jewellery.
We are not using MFC at all here anymore What do you use then? WTL, plain old Win32 API or??? - Anders Money talks, but all mine ever says is "Goodbye!"
-
We are not using MFC at all here anymore What do you use then? WTL, plain old Win32 API or??? - Anders Money talks, but all mine ever says is "Goodbye!"
We're writing a 3D app that will be cross platform, so I am actually writing a GUI library so that our Python console calls methods in classes I have created, the idea being we will rewrite those classes for each platform, and our Python interface will not need to change ( because it's what users will see and the idea is that something created for VB3 PC will work on VB3 Mac, obviously ). For that reason I suggested we dump MFC, because most of our code is using OpenGL anyhow, and I felt that while I am overall not unhappy with MFC as a layer over Win32, adding another layer made me worry about speed, and so I thought add a layer, dump a layer. I hoped to use WTL but everyone complained when I wrote the console in WTL that it slowed down the compile time. So we're using plain vanilla Win32 and I'm finally getting a lot of use out of my copy of Petzhold. I must say I'm really enjoying it as a learning experience, and I think it's helping me in terms of understanding what MFC has been managing behind the scenes for me. Actually I'm going away this weekend and it's to the wire if my MFC Internals book will arrive. I hope it does, so I've got something to do while my wife and her sister play tennis. This is the fifth weekend in a row where my wife has had stuff planned EVERY day. I hardly get a chance for a good block on the PC at night, I've been reading up on connection points for weeks and I'm yet to get a couple of hours to experiment and add them to my project. I'm getting really frustrated. Why did I get married again ??? Christian As I learn the innermost secrets of the around me, they reward me in many ways to keep quiet. Men with pierced ears are better prepared for marriage. They've experienced pain and bought Jewellery.
-
I would like to know how many developers are planning on using MFC 7 (or are already using it)? Why, why not?
Yes, I will use MFC 7 on the occasions I need it. I will probably convert our legacy apps to it as well. Why? Numerous reasons. 1) I hate having to remember stuff about multiple environments. If I have to remember switch settings or quirks in VC6 that don't exist in VC7, i'll be annoyed. Yeah, maybe it'll be a little bit of work to convert stuff to VC7, but once done i'll be a lot happier. 2) MFC 7 is cleaner than MFC 6, has more error checking, and less bloated than MFC 6 (it doesn't include as much stuff during compiles and during execution). 3) MS is always more keen on fixing bugs in the current version than the previous version. If I find a bug, I have a much better chance of having it fixed in a VC7 service pack than a VC6 one. 4) I like the VC7 interface a lot. Of course I don't use MFC much these days, I either write in ATL/WTL or C#. But there are times when I need MFC.
-
We're writing a 3D app that will be cross platform, so I am actually writing a GUI library so that our Python console calls methods in classes I have created, the idea being we will rewrite those classes for each platform, and our Python interface will not need to change ( because it's what users will see and the idea is that something created for VB3 PC will work on VB3 Mac, obviously ). For that reason I suggested we dump MFC, because most of our code is using OpenGL anyhow, and I felt that while I am overall not unhappy with MFC as a layer over Win32, adding another layer made me worry about speed, and so I thought add a layer, dump a layer. I hoped to use WTL but everyone complained when I wrote the console in WTL that it slowed down the compile time. So we're using plain vanilla Win32 and I'm finally getting a lot of use out of my copy of Petzhold. I must say I'm really enjoying it as a learning experience, and I think it's helping me in terms of understanding what MFC has been managing behind the scenes for me. Actually I'm going away this weekend and it's to the wire if my MFC Internals book will arrive. I hope it does, so I've got something to do while my wife and her sister play tennis. This is the fifth weekend in a row where my wife has had stuff planned EVERY day. I hardly get a chance for a good block on the PC at night, I've been reading up on connection points for weeks and I'm yet to get a couple of hours to experiment and add them to my project. I'm getting really frustrated. Why did I get married again ??? Christian As I learn the innermost secrets of the around me, they reward me in many ways to keep quiet. Men with pierced ears are better prepared for marriage. They've experienced pain and bought Jewellery.
Why did I get married again ??? I thought it would have been free and easy (?) access to baby making practice. :-D Michael Martin Pegasystems Pty Ltd Australia martm@pegasystems.com +61 413-004-018 "Don't belong. Never join. Think for yourself. Peace" - Victor Stone
-
Yes, when I need it :rolleyes: . I use MFC for 2 things: one is ISAPI extensions, and the second is GUI. Whenever I don't need these, I try to avoid MFC. I'm not a big fan of CString. I vote pro drink :beer:
-
Why did I get married again ??? I thought it would have been free and easy (?) access to baby making practice. :-D Michael Martin Pegasystems Pty Ltd Australia martm@pegasystems.com +61 413-004-018 "Don't belong. Never join. Think for yourself. Peace" - Victor Stone
You'd have thought it would happen like that, wouldn't you ? Christian As I learn the innermost secrets of the around me, they reward me in many ways to keep quiet. Men with pierced ears are better prepared for marriage. They've experienced pain and bought Jewellery.
-
I would like to know how many developers are planning on using MFC 7 (or are already using it)? Why, why not?
I've used it with VC 4 and 5 and wasn't very happy with it. But, I'm a bit of a control freak when it comes to class frameworks. Borland's OWL in their v4.5 C++ compiler was a nice framework, but they had a hard time keeping up with Microsoft's changing API's. I've been using WTL lately and I'm warming up to it. I don't generally like the way that templates tend to obfuscate code. And I really don't like the macro-madness in MFC, but WTL seems like a reasonable compromise.
