What is the Future of MFC?

[arlef]

I was just wondering if MS is going to continue to support MFC? As with all
this .Net thing going on. Is visual studio 2005 going to support the
creation of MFC applications?


Regards

Arlef

[Tim Ward]

Post by arlef
I was just wondering if MS is going to continue to support MFC? As with all
this .Net thing going on. Is visual studio 2005 going to support the
creation of MFC applications?

Google will show you the last 487 threads on this topic, the most recent
being only a couple of weeks ago.

--
Tim Ward
Brett Ward Limited - www.brettward.co.uk

[Ajay Kalra]

Post by arlef
I was just wondering if MS is going to continue to support MFC?

Yes.

Post by arlef
Is visual studio 2005 going to support the creation of MFC

applications?

Yes.

-----------
Ajay Kalra
***@yahoo.com

[Anthony Wieser]

"Ajay Kalra" <***@yahoo.com> wrote in message news:***@f14g2000cwb.googlegroups.com...
:> I was just wondering if MS is going to continue to support MFC?
:
: Yes.
:
: > Is visual studio 2005 going to support the creation of MFC
: applications?
:
: Yes.

That's not my experience at the moment...

I just tried to build a straightforward MFC dialog application in
Visual C++ 2005 Express Edition Beta 2

I did it by starting in MSVC 6.0, and used the wizard to create a dialog
based MFC app.
Then I imported the project into Visual C++ 2005 Express Edition Beta 2

I was also using the latest Platform SDK (Win 2003 Server SP1)

First, I couldn't get it to recognize my include paths (despite editing ,
and had to set them manually in the build settings.

Then, despite that, I got errors like the following:
C:\Program Files\Microsoft Visual Studio\VC98\MFC\Include\afxwin1.inl(1014)
: error C4430: missing type specifier - int assumed. Note: C++ does not
support default-int
C:\Program Files\Microsoft Visual Studio\VC98\MFC\Include\afxwin1.inl(1016)
: error C4430: missing type specifier - int assumed. Note: C++ does not
support default-int

So, it appears that some C++ compliance has caused the following lines (from
afxwin1.inl) to become illegal:
_AFXWIN_INLINE CMenu::operator==(const CMenu& menu) const
{ return ((HMENU) menu) == m_hMenu; }
_AFXWIN_INLINE CMenu::operator!=(const CMenu& menu) const
{ return ((HMENU) menu) != m_hMenu; }

I've raised this as a bug on the website, but has anyone else
a) tried this
and if so
b) found a workaround?

Anthony Wieser
Wieser Software Ltd

[Ajay Kalra]

I have never gone from VS6 to VS2005 directly. I have not used much of
VS2005 at all. I did go from VS6 to VS2003 for few wizard created
projects and it worked fine.

-----------
Ajay Kalra
***@yahoo.com

[Bo Persson]

Post by Anthony Wieser
:> I was just wondering if MS is going to continue to support MFC?
: Yes.
: > Is visual studio 2005 going to support the creation of MFC
: applications?
: Yes.
That's not my experience at the moment...
I just tried to build a straightforward MFC dialog application in
Visual C++ 2005 Express Edition Beta 2
I did it by starting in MSVC 6.0, and used the wizard to create a dialog
based MFC app.
Then I imported the project into Visual C++ 2005 Express Edition Beta 2
I was also using the latest Platform SDK (Win 2003 Server SP1)
First, I couldn't get it to recognize my include paths (despite editing ,
and had to set them manually in the build settings.
C:\Program Files\Microsoft Visual
Studio\VC98\MFC\Include\afxwin1.inl(1014)

These are the sources for the VC6 version of MFC. That is not compatible
with VC2005.

To continue use MFC, you need the Standard Edition (or higher) version
of VS2005.



Bo Persson

[Anthony Wieser]

: > That's not my experience at the moment...
: >
: > I just tried to build a straightforward MFC dialog application in
: > Visual C++ 2005 Express Edition Beta 2
: >
: These are the sources for the VC6 version of MFC. That is not compatible
: with VC2005.
:
: To continue use MFC, you need the Standard Edition (or higher) version
: of VS2005.
:
:
:
: Bo Persson
:

Having re-read everything carefully, I now notice that although the header
files are included in the platform SDK, the sources aren't. I also hadn't
noticed that the express version didn't explicitly say anything about MFC,
so I've signed up for the BETA for the bigger package.

However, I'm still worried about the errors that will crop up due to the
error C4430: missing type specifier - int assumed. Note: C++ does not
support default-int

Will it be possible to switch this on as a microsoft extension--otherwise I
worry that there will be tons of code to modify.

Anthony Wieser
Wieser Software Ltd

[Mark Randall]

I was under the impression the express edition didnt even include MFC - only
standard and above.

Try in microsoft.public.vc.mfc, I think we were talking about this a few
days ago.
--
- Mark Randall
http://zetech.swehli.com

"Anthony Wieser"

Post by Anthony Wieser
Having re-read everything carefully, I now notice that although the header
files are included in the platform SDK, the sources aren't. I also hadn't
noticed that the express version didn't explicitly say anything about MFC,
so I've signed up for the BETA for the bigger package.
However, I'm still worried about the errors that will crop up due to the
error C4430: missing type specifier - int assumed. Note: C++ does not
support default-int
Will it be possible to switch this on as a microsoft extension--otherwise I
worry that there will be tons of code to modify.
Anthony Wieser
Wieser Software Ltd

[Mark Randall]

Absolutly.
--
- Mark Randall
http://zetech.swehli.com

Post by arlef
I was just wondering if MS is going to continue to support MFC? As with all
this .Net thing going on. Is visual studio 2005 going to support the
creation of MFC applications?
Regards
Arlef