VB .NET not CLS-compliant ?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

e_man_online@hotmail.com - 24 Jul 2006 16:46 GMT

Hi,

I have a Visual Studio 2003 .NET 1.1 project that refers to types from
ADODB like:

CommandTypeEnum, DataTypeEnum and ParameterDirectionEnum
and declares variables and parameters of these types.

When compiling this source code using VStudio 2005 .NET 2.2, all these
types give errors like:

"Type 'ParameterDirectionEnum' is not CLS-compliant"

The type is an Integer in the ADODB library. Why is the compiler
complaining that it's not CLS-compliant? How can I get rid of these
compilation mesages?

Thanks in advance,

Richard

Reply to this Message

Ralph - 24 Jul 2006 18:28 GMT

> Hi,
>
[quoted text clipped - 16 lines]
>
> Richard

ADO and ADO.Net are two different libraries. You can use ADO within a .net
application, but it takes a bit of massage.

Signature

<response type="generic" language="VB.Net">
This newsgroup is for users of Visual Basic version 6.0
and earlier and not the misleadingly named VB.Net
or VB 200x. Solutions, and often even the questions,
for one platform will be meaningless in the other.
When VB.Net was released Microsoft created new newsgroups
devoted to the new platform so that neither group of
developers need wade through the clutter of unrelated
topics. Look for newsgroups with the words "dotnet",
"framework", or "vsnet" in their name.

For the news.microsoft.com news server try these:
news://msnews.microsoft.com/
microsoft.public.dotnet.languages.vb.data
microsoft.public.dotnet.framework.adonet
microsoft.public.dotnet.framework.windowsforms.databinding
</response>

Reply to this Message

VB Forum / Database Access / July 2006

VB .NET not CLS-compliant ?