You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by "Gilles Bayon (JIRA)" <ib...@incubator.apache.org> on 2005/08/13 18:05:54 UTC
[jira] Reopened: (IBATISNET-99) Mark assemblies with CLSCompliant attribute
[ http://issues.apache.org/jira/browse/IBATISNET-99?page=all ]
Gilles Bayon reopened IBATISNET-99:
-----------------------------------
Reopen to avoid forget to remove CLSCompliant attribute when we move to version of Dynamicproxy CLSCompliant .
> Mark assemblies with CLSCompliant attribute
> -------------------------------------------
>
> Key: IBATISNET-99
> URL: http://issues.apache.org/jira/browse/IBATISNET-99
> Project: iBatis for .NET
> Type: Improvement
> Components: DataAccess, DataMapper
> Versions: DataMapper 1.1, DataMapper 1.2.0, DataMapper 1.2.1, DataAccess 1.5, DataAccess 1.6.0, DataAccess 1.6.1, DataAccess 1.7, DataMapper 1.5, DataMapper 1.3
> Reporter: Roelof Blom
> Assignee: Gilles Bayon
> Priority: Minor
> Fix For: DataAccess 1.7, DataMapper 1.3
>
> Assemblies should explicitly state their Cls compliance
> using the CLSCompliant attribute. An assembly without
> this attribute is not CLS-compliant. Assemblies, modules,
> and types can be CLS-compliant even if some parts of
> the assembly, module, or type are not CLS-compliant.
> The following rules apply: 1) If the element is marked
> CLSCompliant, any noncompliant members must have the
> CLSCompliant attribute present with its argument set
> to false. 2) A comparable CLS-compliant alternative
> member must be supplied for each member that is not
> CLS-compliant."
>
> See http://www.gotdotnet.com/team/fxcop/docs/rules.aspx?version=1.32&url=/Design/MarkAssembliesWithClsCompliant.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira