FxCop 1.36 Released!

Question

We've released FxCop 1.36. See the following for more information:

http://blogs.msdn.com/fxcop/archive/2008/08/19/fxcop-1-36-released.aspx 

Answer 1

I installed this last year (v9.0.30729.1), but for the past few weeks FxCop has been telling me that there's an update available. The "update" is the same version; when I download and run the installer, I only get the option to repair or uninstall.

Why is FxCop telling me there's an update when there isn't?

Answer 2

I'm having this same issue.. I have even uninstalled and re-installed, but for the past month it continues to say a new version is available.

Answer 3

Using Fiddler, I can see that the updateinfo.xml file is reporting the latest version as 9.0.30729.17; the download link is still for v9.0.30729.1, which I already have.

GET /feeds/msdn/en-us/fxcop/updateinfo.xml HTTP/1.1
Host: www.microsoft.com

HTTP/1.1 200 OK
Cache-Control: max-age=900
Content-Type: text/xml
Last-Modified: Thu, 16 Jul 2009 23:12:47 GMT
Accept-Ranges: bytes
ETag: "cb51ef6a6ca1:0"
Server: Microsoft-IIS/7.5
P3P: CP="ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI"
X-Powered-By: ASP.NET
Date: Fri, 09 Oct 2009 15:28:23 GMT
Content-Length: 975

<UpdateInfo>
  <LatestVersion>9.0.30729.17 </LatestVersion>
  <DownloadLocation>http://www.microsoft.com/downloads/details.aspx?FamilyID=9aeaa970-f281-4fb0-aba1-d59d7ed09772</DownloadLocation>
  <Message>Microsoft FxCop 1.36 has been released</Message>
  <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
    <SignedInfo>
      <CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315" />
      <SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#dsa-sha1" />
      <Reference URI="">
        <Transforms>
          <Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" />
        </Transforms>
        <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
        <DigestValue>T+JB4uZwR+eJb3CO4uL4KxcHeNI=</DigestValue>
      </Reference>
    </SignedInfo>
    <SignatureValue>jgcoLYHnpkB7krWO6DLN74xd3+o4pQ73U7nj9bZjyaJTvp0BUexrpA==</SignatureValue>
  </Signature>
</UpdateInfo>

Answer 4

Is FxCop still being maintained? This particular issue has been happening for awhile. Also, the guidelines don't appear to be correct for WPF applications.

---

WouldBePenguinite