Issue in migration of VC++6.0 Dll to VC++2010 Dll

Question

1.50/5 (2 votes)

See more:

I am having one project, which is created in VC++6.0 .This project having one exe file and 5 dlls files.

The project is migrate to Visual Studio 2010 from VC++6.0. Now the exe is in C# 2010 and Dlls are in VC++ 2010.

My problem is, I have to access VC++ dll’s class member variables in the C# exe, so for this in VC++ dll’s class, I have added “ref” in the header files.

Below is code snippet of VC++ 2010 dll

Code of ShipInfo.h (header file)

namespace ShipInfoDllNamespace
{
public ref class ShipInfo
{
private:
static float m_fDirection;
}

Code of ShipInfo.cpp (source file)

namespace ShipInfoDllNamespace
{
float ShipInfo::m_fDirection;
}

Now if “ref” is added then I am getting error as –

error C3366: 'ShipInfoDllNamespace::ShipInfo::m_fDirection' : static data members of managed types must be defined within the class definition

-----------------------------------------------------------------------
And if i remove "ref" then NO error, but then i can't access VC++ Dll member variable in C# exe class.

Can anyone advice me how to resolve this issue. Thanks in advance.

Posted 30-Jan-12 18:18pm

nhasmita

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Lakamraju Raghuram · Answer 1 · 2012-01-30T18:38:00

Solution 1

In unmanaged C++, Static data members of classes must be initialized at file scope, while you have to do the same in the class itself in C++/CLI

check this :
http://msdn.microsoft.com/en-us/library/27tfb08h.aspx[^]

Also check this article for intro to mangaed c++. It's good one.
C++/CLI in Action - Instantiating CLI classes[^]

Posted 30-Jan-12 18:38pm

Lakamraju Raghuram

Comments

Sergey Alexandrovich Kryukov 31-Jan-12 1:05am

Good reply, my 5.

You know, I don't feel OP realizes where the migration goes, so I added some clarification in my answer, please see.
--SA

Sergey Alexandrovich Kryukov · Answer 2 · 2012-01-30T19:04:00

You are not migrating from VC++6.0 to VC++ 2010, you are migrating: 1) from native platform to CLR platform implemented by .NET; 2) not from one version of C++ to another one, but from one language to a very different language called C++/CLI.

I'm afraid you do not realize one or both of those two facts.

I'm afraid you might not realize that you don't have to move to .NET. You can stay with native platform; in this case your project would be pretty much backward-compatible (if you don't have anything silly in your legacy code); and the conversion of the projects would be done automatically.

So, I suggest you either stay with native development and C++ or learn .NET and C++/CLI (or some other .NET language(s)), but you probably need to start from scratch. The CLR platform is very different from Windows: it is object-oriented, managed, based on JIT compilation, etc. For a Windows and C++ development the leap is pretty big. (And for developers used to some other languages and systems it would be more than natural; for example, from Ada, Delphi Pascal and more.)

—SA