C++ static method compile error when migrating from .NET 1.1 to 2.0

[KevinMurphyRJLG]

I have a managed C++ class with a number of static methods, all of which are
declared public. After switching from .NET 1.1 to 2.0 (Visual Studio 2003 to
VS 2005), I'm now getting compiler errors like:

error C2248: 'MyHelperClass::MyStaticMethod' : cannot access private member
in class MyHelperClass

I haven't made any code changes in MyHelperClass or the class that calls it.
Any ideas as to why this no longer compiles in VS 2005? Here's a code example:

Class with static methods:

namespace Utils
{
    public __gc class ConversionUtils
    {
    private:
        ConversionUtils(void);
        ~ConversionUtils(void);
 
    public:
        static int ConversionFunction1(int arg);
        static int ConversionFunction2(int arg);
    }
}
 

Calling class (in a different project):

int CallingClass::GetConvertedValue()
{
    return Utils::ConversionUtils::ConversionFunction1(memberVariable);
}

This results in an error like:

error C2248: 'Utils::ConversionUtils::ConversionFunction1' : cannot access
private member declared in class 'Utils::ConversionUtils'
utils.dll : see declaration of 'Utils::ConversionUtils::ConversionFunction1'
utils.dll : see declaration of 'Utils::ConversionUtils'

[kenobewan]

It depends on whether the C++ class is managed or unmanaged code. If it is managed, you can set a normal assembly reference to it. If not, you need to use P/Invoke with the DLLImport or similar attribute. HTH.

[KevinMurphyRJLG]

Both the class with the static methods and the calling class are managed. The project with the calling class does have a reference to the dll that contains the class with the static methods.

It depends on whether the C++ class is managed or unmanaged code. If it is managed, you can set a normal assembly reference to it. If not, you need to use P/Invoke with the DLLImport or similar attribute. HTH.