Consider merging the types defined in 'FFTw_wrapper' with another namespace. Remove all underscores from namespace 'FFTw_wrapper'. Correct the capitalization of 'Tw' in namespace name 'FFTw_wrapper'. No valid permission requests were found for assembly 'FFTw_wrapper'. You should always specify the minimum security permissions using SecurityAction.RequestMinimum. Sign 'FFTw_wrapper' with a strong name key. Add an AssemblyVersion attribute to 'FFTw_wrapper'. 'FFTw_wrapper' should be marked with CLSCompliantAttribute and its value should be true. 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). Correct the capitalization of type name 'FFTCalculator'. Correct the casing of parameter name 'NumeroDeMuestras'. Correct the casing of parameter name 'BufferEntrada'. Correct the casing of parameter name 'BufferSalida'. Assemblies should declare minimum security 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. No valid permission requests were found for assembly '{0}'. You should always specify the minimum security permissions using SecurityAction.RequestMinimum. [none] CriticalError Assemblies should have valid strong names 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). Sign '{0}' with a strong name key. [none] CriticalError Avoid namespaces with few types A namespace should generally have more than five types. Consider merging the types defined in '{0}' with another namespace. [none] Warning Identifiers should be cased correctly 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. Correct the casing of parameter name '{0}'. [none] Error Identifiers should not contain underscores 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. Remove all underscores from namespace '{0}'. [none] Error Long acronyms should be pascal-cased 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. Correct the capitalization of type name '{0}'. [none] Error Mark assemblies with assembly version 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. Add an AssemblyVersion attribute to '{0}'. [none] Error Mark assemblies with CLSCompliant 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. '{0}' should be marked with CLSCompliantAttribute and its value should be true. [none] Error Mark assemblies with ComVisible 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. 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). [none] CriticalError, Error Short acronyms should be uppercase 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. Correct the capitalization of '{0}' in namespace name '{1}'. [none] Error Category Collapse All Check Id Error error(s) Line <Location not stored in Pdb> Project Rule Rule Description Source Target Warning warning(s) Microsoft Visual Studio 2005 Code Analysis Report