<?xml version="1.0" encoding="utf-8"?>
|
<?xml-stylesheet type="text/xsl" href="c:\archivos de programa\microsoft visual studio 8\team tools\static analysis tools\fxcop\Xml\CodeAnalysisReport.Xsl"?>
|
<FxCopReport Version="8">
|
<Namespaces>
|
<Namespace Name="FFTw_wrapper">
|
<Messages>
|
<Message TypeName="AvoidNamespacesWithFewTypes" Category="Microsoft.Design" CheckId="CA1020" Status="Active" Created="2007-02-21 12:37:07Z" FixCategory="Breaking">
|
<Issue Certainty="50" Level="Warning">Consider merging the types defined in 'FFTw_wrapper' with another namespace.</Issue>
|
</Message>
|
<Message TypeName="IdentifiersShouldNotContainUnderscores" Category="Microsoft.Naming" CheckId="CA1707" Status="Active" Created="2007-02-21 12:37:07Z" FixCategory="Breaking">
|
<Issue Name="Namespace" Certainty="95" Level="Error">Remove all underscores from namespace 'FFTw_wrapper'.</Issue>
|
</Message>
|
<Message TypeName="ShortAcronymsShouldBeUppercase" Category="Microsoft.Naming" CheckId="CA1706" Status="Active" Created="2007-02-21 12:37:07Z" FixCategory="Breaking">
|
<Issue Name="Namespace" Certainty="85" Level="Error">Correct the capitalization of 'Tw' in namespace name 'FFTw_wrapper'.</Issue>
|
</Message>
|
</Messages>
|
</Namespace>
|
</Namespaces>
|
<Targets>
|
<Target Name="c:\Documents and Settings\Carlos Vela\Mis documentos\Visual Studio 2005\Projects\Proyectos PosteIP\E301_Control_Demo V01\Auxliar Projects\SignalViewer\FFTw_wrapper\Debug\FFTw_wrapper.dll">
|
<Modules>
|
<Module Name="fftw_wrapper.dll">
|
<Messages>
|
<Message TypeName="AssembliesShouldDeclareMinimumSecurity" Category="Microsoft.Usage" CheckId="CA2209" Status="Active" Created="2007-02-21 12:37:07Z" FixCategory="Breaking">
|
<Issue Certainty="95" Level="CriticalError">No valid permission requests were found for assembly 'FFTw_wrapper'. You should always specify the minimum security permissions using SecurityAction.RequestMinimum.</Issue>
|
</Message>
|
<Message TypeName="AssembliesShouldHaveValidStrongNames" Category="Microsoft.Design" CheckId="CA2210" Status="Active" Created="2007-02-21 12:37:07Z" FixCategory="NonBreaking">
|
<Issue Name="NoStrongName" Certainty="95" Level="CriticalError">Sign 'FFTw_wrapper' with a strong name key.</Issue>
|
</Message>
|
<Message TypeName="MarkAssembliesWithAssemblyVersion" Category="Microsoft.Design" CheckId="CA1016" Status="Active" Created="2007-02-21 12:37:07Z" FixCategory="NonBreaking">
|
<Issue Certainty="95" Level="Error">Add an AssemblyVersion attribute to 'FFTw_wrapper'.</Issue>
|
</Message>
|
<Message TypeName="MarkAssembliesWithClsCompliant" Category="Microsoft.Design" CheckId="CA1014" Status="Active" Created="2007-02-21 12:37:07Z" FixCategory="NonBreaking">
|
<Issue Name="NoAttr" Certainty="95" Level="Error">'FFTw_wrapper' should be marked with CLSCompliantAttribute and its value should be true.</Issue>
|
</Message>
|
<Message TypeName="MarkAssembliesWithComVisible" Category="Microsoft.Design" CheckId="CA1017" Status="Active" Created="2007-02-21 12:37:07Z" FixCategory="NonBreaking">
|
<Issue Name="NoAttribute" Certainty="95" Level="CriticalError">Mark 'FFTw_wrapper' as ComVisible(false) at the assembly level, then mark all types within the assembly that should be exposed to Com clients as ComVisible(true).</Issue>
|
</Message>
|
</Messages>
|
<Namespaces>
|
<Namespace Name="FFTw_wrapper">
|
<Types>
|
<Type Name="FFTCalculator" Kind="Class" Accessibility="Public" ExternallyVisible="True">
|
<Messages>
|
<Message TypeName="LongAcronymsShouldBePascalCased" Category="Microsoft.Naming" CheckId="CA1705" Status="Active" Created="2007-02-21 12:37:07Z" FixCategory="Breaking">
|
<Issue Name="Type" Certainty="85" Level="Error">Correct the capitalization of type name 'FFTCalculator'.</Issue>
|
</Message>
|
</Messages>
|
<Members>
|
<Member Name=".ctor(System.Int32,System.Int16[],System.Double[])" Kind="Method" Static="False" Accessibility="Public" ExternallyVisible="True">
|
<Messages>
|
<Message Id="0#" TypeName="IdentifiersShouldBeCasedCorrectly" Category="Microsoft.Naming" CheckId="CA1709" Status="Active" Created="2007-02-21 12:37:07Z" FixCategory="Breaking">
|
<Issue Name="Parameter" Certainty="95" Level="Error" Path="c:\documents and settings\carlos vela\mis documentos\visual studio 2005\projects\proyectos posteip\e301_control_demo v01\auxliar projects\signalviewer\fftw_wrapper" File="fftw_wrapper.cpp" Line="19">Correct the casing of parameter name 'NumeroDeMuestras'.</Issue>
|
</Message>
|
<Message Id="1#" TypeName="IdentifiersShouldBeCasedCorrectly" Category="Microsoft.Naming" CheckId="CA1709" Status="Active" Created="2007-02-21 12:37:07Z" FixCategory="Breaking">
|
<Issue Name="Parameter" Certainty="95" Level="Error" Path="c:\documents and settings\carlos vela\mis documentos\visual studio 2005\projects\proyectos posteip\e301_control_demo v01\auxliar projects\signalviewer\fftw_wrapper" File="fftw_wrapper.cpp" Line="19">Correct the casing of parameter name 'BufferEntrada'.</Issue>
|
</Message>
|
<Message Id="2#" TypeName="IdentifiersShouldBeCasedCorrectly" Category="Microsoft.Naming" CheckId="CA1709" Status="Active" Created="2007-02-21 12:37:07Z" FixCategory="Breaking">
|
<Issue Name="Parameter" Certainty="95" Level="Error" Path="c:\documents and settings\carlos vela\mis documentos\visual studio 2005\projects\proyectos posteip\e301_control_demo v01\auxliar projects\signalviewer\fftw_wrapper" File="fftw_wrapper.cpp" Line="19">Correct the casing of parameter name 'BufferSalida'.</Issue>
|
</Message>
|
</Messages>
|
</Member>
|
</Members>
|
</Type>
|
</Types>
|
</Namespace>
|
</Namespaces>
|
</Module>
|
</Modules>
|
</Target>
|
</Targets>
|
<Rules>
|
<Rule TypeName="AssembliesShouldDeclareMinimumSecurity" Category="Microsoft.Usage" CheckId="CA2209">
|
<Name>Assemblies should declare minimum security</Name>
|
<Description>Permission requests prevent security exceptions from being thrown after code in an assembly has already begun executing. If permission requests are specified on an assembly, the assembly will not load at runtime if it has insufficient permissions. To resolve violations of this rule, add attributes that specify what permissions the assembly will demand or might demand, and what permissions it does not want granted. To specify required permissions, use SecurityAction.Minimum. To specify permissions that the assembly might demand, use SecurityAction.RequestOptional. To specify permissions that the assembly must not be granted, use SecurityAction.RequestRefuse.</Description>
|
<Resolution Name="Default">No valid permission requests were found for assembly '{0}'. You should always specify the minimum security permissions using SecurityAction.RequestMinimum.</Resolution>
|
<Owner />
|
<Email>[none]</Email>
|
<MessageLevel Certainty="95">CriticalError</MessageLevel>
|
<File Name="UsageRules.dll" Version="8.0.0.0" />
|
</Rule>
|
<Rule TypeName="AssembliesShouldHaveValidStrongNames" Category="Microsoft.Design" CheckId="CA2210">
|
<Name>Assemblies should have valid strong names</Name>
|
<Description>Either the assembly has no strong name, an invalid one, or the strong name is valid only because of the computer configuration. The assembly should not be deployed in this state. The most common causes of this are: 1) The assembly's contents were modified after it was signed. 2) The signing process failed. 3) The assembly was delay-signed. 4) A registry key existed that allowed the check to pass (where it would not have otherwise).</Description>
|
<Resolution Name="NoStrongName">Sign '{0}' with a strong name key.</Resolution>
|
<Owner />
|
<Email>[none]</Email>
|
<MessageLevel Certainty="95">CriticalError</MessageLevel>
|
<File Name="DesignRules.dll" Version="8.0.0.0" />
|
</Rule>
|
<Rule TypeName="AvoidNamespacesWithFewTypes" Category="Microsoft.Design" CheckId="CA1020">
|
<Name>Avoid namespaces with few types</Name>
|
<Description>A namespace should generally have more than five types.</Description>
|
<Resolution Name="Default">Consider merging the types defined in '{0}' with another namespace.</Resolution>
|
<Owner />
|
<Email>[none]</Email>
|
<MessageLevel Certainty="50">Warning</MessageLevel>
|
<File Name="DesignRules.dll" Version="8.0.0.0" />
|
</Rule>
|
<Rule TypeName="IdentifiersShouldBeCasedCorrectly" Category="Microsoft.Naming" CheckId="CA1709">
|
<Name>Identifiers should be cased correctly</Name>
|
<Description>Type, namespace, and member identifiers are pascal-cased. Parameter identifiers are camel-cased. The pascal-casing convention capitalizes the first letter of each word, as in BackColor. The camel-casing convention formats the first letter of the first word in lowercase and capitalizes the first letter of all subsequent words, as in backgroundColor.</Description>
|
<Resolution Name="Parameter">Correct the casing of parameter name '{0}'.</Resolution>
|
<Owner />
|
<Email>[none]</Email>
|
<MessageLevel Certainty="95">Error</MessageLevel>
|
<File Name="NamingRules.dll" Version="8.0.0.0" />
|
</Rule>
|
<Rule TypeName="IdentifiersShouldNotContainUnderscores" Category="Microsoft.Naming" CheckId="CA1707">
|
<Name>Identifiers should not contain underscores</Name>
|
<Description>Do not use underscores when specifying identifiers. Some generated Visual Studio identifiers for applications contain underscore characters. Underscore characters should generally be avoided in public identifiers.</Description>
|
<Resolution Name="Namespace">Remove all underscores from namespace '{0}'.</Resolution>
|
<Owner />
|
<Email>[none]</Email>
|
<MessageLevel Certainty="95">Error</MessageLevel>
|
<File Name="NamingRules.dll" Version="8.0.0.0" />
|
</Rule>
|
<Rule TypeName="LongAcronymsShouldBePascalCased" Category="Microsoft.Naming" CheckId="CA1705">
|
<Name>Long acronyms should be pascal-cased</Name>
|
<Description>Acronyms of three or more letters should be Pascal-cased. For example, use XmlSpace rather than XMLSpace. A violation of this rule might be required for compatibility with existing, non-managed symbol schemes. In general, however, these symbols should not be visible outside the assembly that uses them.</Description>
|
<Resolution Name="Type">Correct the capitalization of type name '{0}'.</Resolution>
|
<Owner />
|
<Email>[none]</Email>
|
<MessageLevel Certainty="85">Error</MessageLevel>
|
<File Name="NamingRules.dll" Version="8.0.0.0" />
|
</Rule>
|
<Rule TypeName="MarkAssembliesWithAssemblyVersion" Category="Microsoft.Design" CheckId="CA1016">
|
<Name>Mark assemblies with assembly version</Name>
|
<Description>Assemblies should use version numbers. The version number is considered part of an assembly's identity. Versioning is applied by means of the AssemblyVersion attribute.</Description>
|
<Resolution Name="Default">Add an AssemblyVersion attribute to '{0}'.</Resolution>
|
<Owner />
|
<Email>[none]</Email>
|
<MessageLevel Certainty="95">Error</MessageLevel>
|
<File Name="DesignRules.dll" Version="8.0.0.0" />
|
</Rule>
|
<Rule TypeName="MarkAssembliesWithClsCompliant" Category="Microsoft.Design" CheckId="CA1014">
|
<Name>Mark assemblies with CLSCompliant</Name>
|
<Description>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.</Description>
|
<Resolution Name="NoAttr">'{0}' should be marked with CLSCompliantAttribute and its value should be true.</Resolution>
|
<Owner />
|
<Email>[none]</Email>
|
<MessageLevel Certainty="95">Error</MessageLevel>
|
<File Name="DesignRules.dll" Version="8.0.0.0" />
|
</Rule>
|
<Rule TypeName="MarkAssembliesWithComVisible" Category="Microsoft.Design" CheckId="CA1017">
|
<Name>Mark assemblies with ComVisible</Name>
|
<Description>The System.Runtime.InteropServices.ComVisible attribute indicates whether COM clients can use the library. Good design dictates that developers explicitly indicate COM visibility. The default value for this attribute is 'true'. However, the best design is to mark the assembly ComVisible false, and then mark types, interfaces, and individual members as ComVisible true, as appropriate.</Description>
|
<Resolution Name="NoAttribute">Mark '{0}' as ComVisible(false) at the assembly level, then mark all types within the assembly that should be exposed to Com clients as ComVisible(true).</Resolution>
|
<Owner />
|
<Email>[none]</Email>
|
<MessageLevel Certainty="95">CriticalError, Error</MessageLevel>
|
<File Name="DesignRules.dll" Version="8.0.0.0" />
|
</Rule>
|
<Rule TypeName="ShortAcronymsShouldBeUppercase" Category="Microsoft.Naming" CheckId="CA1706">
|
<Name>Short acronyms should be uppercase</Name>
|
<Description>Two letter acronyms should be upper-cased. For example, use System.IO instead of System.Io. Although it may be common practice for some two letter acronyms to not be fully capitalized, violations of this rule should not be excluded for this reason. For example, 'DbConnection', is common but incorrect; use DBConnection. A violation of this rule might be required for compatibility with existing, non-managed symbol schemes. In general, however, these symbols should not be visible outside the assembly that uses them.</Description>
|
<Resolution Name="Namespace">Correct the capitalization of '{0}' in namespace name '{1}'.</Resolution>
|
<Owner />
|
<Email>[none]</Email>
|
<MessageLevel Certainty="85">Error</MessageLevel>
|
<File Name="NamingRules.dll" Version="8.0.0.0" />
|
</Rule>
|
</Rules>
|
<Localized>
|
<String Key="Category">Category</String>
|
<String Key="CollapseAll">Collapse All</String>
|
<String Key="CheckId">Check Id</String>
|
<String Key="Error">Error</String>
|
<String Key="Errors">error(s)</String>
|
<String Key="Line">Line</String>
|
<String Key="LocationNotStoredInPdb"><Location not stored in Pdb></String>
|
<String Key="Project">Project</String>
|
<String Key="Rule">Rule</String>
|
<String Key="RuleDescription">Rule Description</String>
|
<String Key="Source">Source</String>
|
<String Key="Target">Target</String>
|
<String Key="Warning">Warning</String>
|
<String Key="Warnings">warning(s)</String>
|
<String Key="ReportTitle">Microsoft Visual Studio 2005 Code Analysis Report</String>
|
</Localized>
|
</FxCopReport>
|
