VS 2003 to VS2005 upgrade

19 Jun 2006 8:56 PM

BK

I am converting a rather large solution from VS 2003 to VS 2005. As I
understand it, the bulk of the conversion is really just changing the
project and solution files to the new format.

It completed ok, but I have a lot of errors and warnings, 17 errors and
260 warnings. The errors seem to all relate to dlls written in VS 2003
that haven't been converted and recompiled. The references are to the
dlls, NOT the projects. A typical error is:

Warning 1 Type of member 'BravoMessage' is not CLS-compliant.

What does it mean that a member is not CLS-compliant?

20 Jun 2006 6:00 AM

Cor Ligthert [MVP]

BK,

>
> What does it mean that a member is not CLS-compliant?
>

It means that by intance you (probably) cannot use the created dll in C#

(Do you have DirectX in your code, there I have seen this?)

Cor

20 Jun 2006 8:47 AM

M. Posseth

See

http://msdn2.microsoft.com/en-us/library/k5645wwb.aspx

and

http://msdn2.microsoft.com/en-us/library/bhc3fa7f(VS.80).aspx

as you see is all old code marked as non compliant as it does not have the
necesary clscompliant attribute set

recompiling the dll`s in VS.Net 2005 should solve the problem

regards

Michel Posseth [MCP]

Show quoteHide quote

"BK" wrote:

> I am converting a rather large solution from VS 2003 to VS 2005. As I
> understand it, the bulk of the conversion is really just changing the
> project and solution files to the new format.
>
> It completed ok, but I have a lot of errors and warnings, 17 errors and
> 260 warnings. The errors seem to all relate to dlls written in VS 2003
> that haven't been converted and recompiled. The references are to the
> dlls, NOT the projects. A typical error is:
>
> Warning 1 Type of member 'BravoMessage' is not CLS-compliant.
>
> What does it mean that a member is not CLS-compliant?
>
>

20 Jun 2006 12:05 PM

BK

M. Posseth wrote:
Show quoteHide quote

> See
>
>
> http://msdn2.microsoft.com/en-us/library/k5645wwb.aspx
>
> and
>
> http://msdn2.microsoft.com/en-us/library/bhc3fa7f(VS.80).aspx
>
>
> as you see is all old code marked as non compliant as it does not have the
> necesary clscompliant attribute set
>
> recompiling the dll`s in VS.Net 2005 should solve the problem
>
> regards
>
> Michel Posseth [MCP]
>

Thanks, that helped. Now on to my next problem (in another thread)