Minimally implemented code, with an attribute [assembly:
CLSCompliantAttribute(true)] in the assemblyinfo.cs compiles just fine (is
it possibly the data INSIDE the dataset that could invalidate its
compliancy?):
using System;
using System.Data;
namespace ConsoleApplication1
{
/// <summary>
/// Summary description for Class1.
/// </summary>
class Class1
{
/// <summary>
/// The main entry point for the application.
/// </summary>
[STAThread]
static void Main(string[] args)
{
Class2 class2 = new Class2();
DataSet newDs = class2.getDataSet();
}
}
}
using System;
using System.Data;
namespace ConsoleApplication1
{
/// <summary>
/// Summary description for Class2.
/// </summary>
public class Class2
{
public Class2()
{
//
// TODO: Add constructor logic here
//
}
public DataSet getDataSet()
{
DataSet newDS = new DataSet("newDatSet");
return newDS;
}
}
}
However, earlier today I was thinking:
Evidence seems to indicate that they Datasets are not CLS compliant.
In Googling, I found a few comments like:
I'm a little concerned about passing datasets on a public interface.
Until someone can let me know that cross-platform development won't be
hindered by using a dataset on a public interface (Dataset is not CLS
Compliant) I'm going to try and not use them in classes that I would
consider libraries for my own code re-use. I wish someone from Microsoft
would way in on that little issue. Paul
Eventually, I wound my way to the ECMA site
(http://www.ecma-international.org/)
List: http://www.ecma-international.org/pu...s/Standard.htm
C# Standard:
http://www.ecma-international.org/pu...s/Ecma-334.htm (CLS)
From Appendix D Standard Library I culled the following namespaces:
// Namespace: System, Library: BCL
// Namespace: System, Library: ExtendedNumerics
// Namespace: System.Collections, Library: BCL
// Namespace: System.Diagnostics, Library: BCL
// Namespace: System.Globalization, Library: BCL
// Namespace: System.Security, Library: BCL
// Namespace: System.Security.Permissions, Library: BCL
// Namespace: System.Text, Library: BCL
// Namespace: System.Threading, Library: BCL
(Note there is no System.Data namespace)
My speculation trail is rather short. If the intent of CLS is to promote
cross-platform development and cross language development then how do you
tell java or small talk or any non-ms type language what a DataSet is?
This is not to say that a DataSet cannot be used privately, it's just that a
DataSet type cannot be exposed in any public member.
FWI, this is an inferred conclusion. I have not seen anything concrete that
says yea or nay.
Thoughts appreciated. Thanks!
Rob
