.NET: AssemblyVersion vs. AssemblyFileVersion in WER? RRS feed

  • Question

  • Hi


    I have an assembly where the AssemblyVersion and the AssemblyFileVersion are different, e.g.:


    [assembly: AssemblyVersion("")]
    [assembly: AssemblyFileVersion("")]


    When creating a mapping file using Product Feedback Mapping Tool, I only see the AssemblyFileVersion versions (e.g. in the mapping file, no sign of the AssemblyVersion (e.g.


    Snippet from the generated mapping file:


        <MATCHING_FILE NAME="BK.ENM.EvaluateWer.Client.exe"
                       BIN_FILE_VERSION="" BIN_PRODUCT_VERSION=""
                       PRODUCT_NAME="BK.ENM.EvaluateWer.Client" FILE_VERSION=""


    When crashing my application and looking at the report in Problem Reports and Solutions, I only see the AssemblyVersion (e.g. in the report. When monitoring network traffic when sending the report to Microsoft I also only see AssemblyVersion (e.g.


    The URL as it looks when sending the report containing the version number:


    http://watson.microsoft.com/StageOne/Generic/CLR20r3/bk_enm_evaluatewer _client_exe/1_2_7_0/48fe1ede/BK_ENM_SomeLibrary/1_7_2_0/48fe1ede/3/a/ 314WNAJ5ISRISOEGCAJ0K2FYJ3UPSL0Z.htm?LCID=1030& OS=6.0.6001.2.00030110.


    How can WER match a submitted report with an uploaded product mapping when the report and product mapping contains different version number?


    It was my understanding that the version number was part of the key used to match reports with products/customers?


    I am of cause asking because my reports are not turning up on the winqual site.




    • Moved by Max Wang_1983 Tuesday, April 26, 2011 4:57 PM forum consolidation (From:Windows Error Reporting for ISVs)
    Friday, October 24, 2008 8:54 AM


  • Hi,


    This is a known problem with the mapping tool, it does not create the right matching information for managed code. Please send your binary information to wer@microsoft.com and someone will assist you.




    Monday, November 24, 2008 12:16 AM