Errors in VC.Net porting

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi all,
I am porting an code written in VC++ to VC.Net to make it manage. But in
Managed VC we dont use "const" keyboard at all. but my code is using it very
frequently, so is their any alternative to it or we have to remove the
"const" keyword from our code completely. Please suggest me the solution.
Secondly i am getting one error as::
error C4439: 'function_name' : function definition with a managed type in
the signature must have a __clrcall calling convention.
code is::extern "C" __declspec(dllexport) String* APIENTRY function_name(
String* s).
Please help me out from these errors.
Thanks.
 
I am porting an code written in VC++ to VC.Net to make it manage. But in
Managed VC we dont use "const" keyboard at all. but my code is using it very
frequently, so is their any alternative to it or we have to remove the
"const" keyword from our code completely.
Click to expand...

You should still be able to use const in those parts of your code that
are still native C++, but as you've found, there's not the same notion
of const in the managed world.

BTW, you mention managed VC - if that means versions prior to VS2005,
you might be wise to move to VS2005 and use the much neater C++/CLI.

Dave
 
Thanks David for this suggestion. but you have not answered my second
question :: i am getting this error ::
error C4439: 'function_name' : function definition with a managed type in
the signature must have a __clrcall calling convention.

my code is::extern "C" __declspec(dllexport) String* APIENTRY function_name(
String* s).
Please help me out from these errors.
 
error C4439: 'function_name' : function definition with a managed type in
the signature must have a __clrcall calling convention.

my code is::extern "C" __declspec(dllexport) String* APIENTRY function_name(
String* s).
Please help me out from these errors.
Click to expand...

Presumably you need to specify __clrcall. Have you tried adding it ?

Dave
 
Dipesh_Sharma said:
Thanks David for this suggestion. but you have not answered my second
question :: i am getting this error ::
error C4439: 'function_name' : function definition with a managed type in
the signature must have a __clrcall calling convention.

my code is::extern "C" __declspec(dllexport) String* APIENTRY function_name(
String* s).
Please help me out from these errors.
Click to expand...

Dipesh:

I am not an expert on managed code, but I am sure extern "C" is not
allowed on a function with managed types in the signature.

It would appear you are trying to convert your entire application to use
managed types. If you want to do this you might as well rewrite the
whole application in C#. The big advantage of Managed C++ (or C++/CLI)
is that you can easily mix managed and unmanaged code in your
application, and you do not seem to be taking advantage of this.

IMHO, you should also take serious note of David Lowndes' suggestion to
move to VS2005. You can also use the latest beta version of VS2008
(which is free). Managed C++ as used in Vs2002 and VS2003 is obsolete,
and IMHO it would be a huge mistake to migrate existing unmanaged code
to it.
 
HI david yes you were right that i am porting my code written in VC++ to make
it managed. I am working on VS2005, and i a not able to remove the error
c4439 of __clrcall. Please help me by providing the exact syntax of exporting
the previously written functions in VC++ to export them in VC.Net.
My code is like::extern "C" __declspec(dllexport) String* APIENTRY
function_name( String* s). And how should i mix both native & managed code in
a single project??
Thanks.
 
Dipesh_Sharma said:
HI david yes you were right that i am porting my code written in VC++ to make
it managed. I am working on VS2005, and i a not able to remove the error
c4439 of __clrcall. Please help me by providing the exact syntax of exporting
the previously written functions in VC++ to export them in VC.Net.
My code is like::extern "C" __declspec(dllexport) String* APIENTRY
function_name( String* s). And how should i mix both native & managed code in
a single project??
Click to expand...

Dipesh:

Maybe I am not clear what you are doing. What is String? If it is
managed and you are using VS2005, then you should be using String^, not
String*.

But my point was that in C++/CLI you do not need to convert each and
every function to managed.

To mix managed and unmanaged code you just do it (that's why it's called
IJW - It Just Works), though there are things you cannot do. I am no
expert here, but I think managed code can generally call unmanaged code,
but not vice-versa.

A good introductory book on C++/CLI is Ivor Horton's "Beginning C++ 2005."
 
Back
Top