|
<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="c:\program files\microsoft visual studio 8\team tools\static analysis tools\fxcop\Xml\CodeAnalysisReport.Xsl"?>
<FxCopReport Version="8">
<Targets>
<Target Name="C:\Documents and Settings\silvat\My Documents\MaryKay.Reporting.MSBuild.Tasks\bin\Debug\Silvaware.MSBuild.Tasks.dll">
<Modules>
<Module Name="silvaware.msbuild.tasks.dll">
<Messages>
<Message TypeName="AssembliesShouldHaveValidStrongNames" Category="Microsoft.Design" CheckId="CA2210" Status="Active" Created="2006-06-21 20:09:06Z" FixCategory="NonBreaking">
<Issue Name="NoStrongName" Certainty="95" Level="CriticalError">Sign 'Silvaware.MSBuild.Tasks' with a strong name key.</Issue>
</Message>
</Messages>
</Module>
</Modules>
</Target>
</Targets>
<Rules>
<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>
</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>
|
By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.
If a file you wish to view isn't highlighted, and is a text file (not binary), please
let us know and we'll add colourisation support for it.
Thiago started programming on Turbo Pascal at age 17, and quickly moved on to java and VB6, and finally landing on .NET. He has implemented custom .NET applications and BI Reporting solutions for many clients.
Thiago has co-authored a couple of SQL Server Reporting Services books, and also dabbles in SharePoint and many things Microsoft.
He is currently an architect/consultant for a specialized consulting firm in the Dallas area.