converting mc++ projetcs to mixed mode

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

bonk - 20 Oct 2005 16:19 GMT

This article

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vcmex/html/vcco
nconvertingmanagedextensionsforcprojectsfrompureintermediatelanguagetomixedmode.
asp

seems to be somewhat out of date. Not all of it seem to apply to vs 2005
(beta 2) and c++/CLI. I followed the instructions given there but
using vs 2005 beta 2 I get some warnings about depreciation:

warning CRT1001: _vcclrit.h is deprecated
warning C4996: '__lock_handle' was declared deprecated
warning C4996: '__terminated' was declared deprecated
warning C4996: '__initialized' was declared deprecated
warning C4996: '__initialized' was declared deprecated
warning C4996: '__lock_handle' was declared deprecated
warning C4996: '__lock_handle' was declared deprecated
warning C4996: '__initialized' was declared deprecated
warning C4996: '__terminated' was declared deprecated
warning C4996: '__terminated' was declared deprecated
warning C4996: '__lock_handle' was declared deprecated
warning C4996: '__crt_dll_initialize' was declared deprecated
warning C4996: '__crt_dll_terminate' was declared deprecated
warning C4793: 'found an intrinsic not supported in managed code' :
causes native code generation for function 'NtCurrentTeb'
d:\programme\microsoft visual studio 8\vc\platformsdk\include\winnt.h    9585
warning LNK4098: defaultlib 'msvcrtd.lib' conflicts with use of other
libs; use /NODEFAULTLIB:library    WPFControls
Warning    16    warning LNK4248: unresolved typeref token (01000012) for
'_TEB'; image may not run    WPFControls.obj

The cause of most of the above warnings are the two function that this
article suggest to add for initialisation and termination.

Can you comment on what parts of the above atricle still apply to vs
2005 and c++/CLI and what I need to do especially for c++/CLI. What
issues when creating mixed mode dlls still exist in c++/CLI and what
have been resolved ?

Reply to this Message

Carl Daniel [VC++ MVP] - 20 Oct 2005 16:42 GMT

> Can you comment on what parts of the above atricle still apply to vs
> 2005 and c++/CLI and what I need to do especially for c++/CLI. What
> issues when creating mixed mode dlls still exist in c++/CLI and what
> have been resolved ?

I believe the answer is that nothing in that article is relevant to VC++
2005. The issues discussed in the article are all related to the mixed-mode
DLL loader lock issue which is fully addressed by the 2.0 CLR and the 2005
C++ compiler.

-cd

Reply to this Message

bonk - 20 Oct 2005 16:53 GMT

I think I found the answer to the _vcclrit.h problem:
http://msdn2.microsoft.com/en-us/library/ms173267(en-us,vs.80).aspx

I just do not need the init.cpp codesnipped anymore. Actaully it seems
that the whole article does not apply to c++/CLI. Looks like there are
no issues to watch out for in mixed mode dlls anymore when using vs 2005.

bonk schrieb:

> This article
>
[quoted text clipped - 33 lines]
> issues when creating mixed mode dlls still exist in c++/CLI and what
> have been resolved ?

Reply to this Message

William DePalo [MVP VC++] - 20 Oct 2005 17:19 GMT

> I just do not need the init.cpp codesnipped anymore. Actaully it seems
> that the whole article does not apply to c++/CLI. Looks like there are no
> issues to watch out for in mixed mode dlls anymore when using vs 2005.

Sorry about that.

I should have mentioned that the article I cited in an earlier post to you
described a shortcoming of VS.Net 2002/2003.

Regards,
Will

Reply to this Message

bonk - 21 Oct 2005 17:14 GMT

William DePalo [MVP VC++] schrieb:

>>I just do not need the init.cpp codesnipped anymore. Actaully it seems
>>that the whole article does not apply to c++/CLI. Looks like there are no
[quoted text clipped - 7 lines]
> Regards,
> Will

There is one thing in thar article that still applies:

Link with /NOENTRY.

is that correct ?

Reply to this Message

converting mc++ projetcs to mixed mode

Free Magazines