MFC conflict with .NET

[ClydeL]

I'm trying to add some CLR code to a legacy VC6.0 code. I've compiled with
the 3005 compiler and eliminated the conflicts in debug mode. Adding the
/CLR option and compiling in release mode has not been successful.

As a test, I built a wizard generated mfc application using doc.view. It
complies without .clr just fine. Switching to /clr for the whole project
generates 8 link warnings, LNK4248.

When I try to compile only one module with /clr (which is what I would like
to do with the legacy app), I get 33 warnings of C4744 and 4 warnings of
LNK4248.

Again, this is with code generated by the mfc wizard. What gives? Am I to
ignore the warnings?

[Bruno van Dooren]

Hi,

Those linker warnings can be expected, it seems. If I understand Ronald
Laeremans correctly, they are harmless in VC2005.
http://www.mcse.ms/archive108-2004-10-1183198.html

The C4744 warnings are caused by this, according to MSDN:
C4744 is emitted only when files are compiled with /GL. For more
information, see /GL (Whole Program Optimization).

disabling whole program optimization shoulod take care of that, then.

kind regards,
Bruno.

"ClydeL" <Cl****@discussions.microsoft.com> wrote in message
news:9B**********************************@microsof t.com...

I'm trying to add some CLR code to a legacy VC6.0 code. I've compiled
with
the 3005 compiler and eliminated the conflicts in debug mode. Adding the
/CLR option and compiling in release mode has not been successful.

As a test, I built a wizard generated mfc application using doc.view. It
complies without .clr just fine. Switching to /clr for the whole project
generates 8 link warnings, LNK4248.

When I try to compile only one module with /clr (which is what I would
like
to do with the legacy app), I get 33 warnings of C4744 and 4 warnings of
LNK4248.

Again, this is with code generated by the mfc wizard. What gives? Am I
to
ignore the warnings?

[ClydeL]

Thanks for the info.

"Bruno van Dooren" wrote:

Hi,

Those linker warnings can be expected, it seems. If I understand Ronald
Laeremans correctly, they are harmless in VC2005.
http://www.mcse.ms/archive108-2004-10-1183198.html

The C4744 warnings are caused by this, according to MSDN:
C4744 is emitted only when files are compiled with /GL. For more
information, see /GL (Whole Program Optimization).

disabling whole program optimization shoulod take care of that, then.

kind regards,
Bruno.

"ClydeL" <Cl****@discussions.microsoft.com> wrote in message
news:9B**********************************@microsof t.com...

I'm trying to add some CLR code to a legacy VC6.0 code. I've compiled
with
the 3005 compiler and eliminated the conflicts in debug mode. Adding the
/CLR option and compiling in release mode has not been successful.

As a test, I built a wizard generated mfc application using doc.view. It
complies without .clr just fine. Switching to /clr for the whole project
generates 8 link warnings, LNK4248.

When I try to compile only one module with /clr (which is what I would
like
to do with the legacy app), I get 33 warnings of C4744 and 4 warnings of
LNK4248.

Again, this is with code generated by the mfc wizard. What gives? Am I
to
ignore the warnings?