BUG: Event Log Data is Incorrect when Importing from CSV File

ID: Q242967


The information in this article applies to:
  • Microsoft Visual Studio, Enterprise Edition 6.0


SYMPTOMS

When importing a modified comma-separated variable file (.csv) into Visual Studio Analyzer, the resulting Event log contains incorrect data.


CAUSE

The order of the standard fields has changed.


RESOLUTION

Do not rearrange the order of the standard fields in the .csv file. If the .csv file contains custom fields, make sure that they are after the standard fields. The custom fields can appear in any order as long as they are after the standard fields.


STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.


MORE INFORMATION

Steps to Reproduce Behavior

  1. Create a Visual Studio Analyzer project, capture some events by starting (or stopping) Internet Explorer.


  2. Once you have captured some events, stop recording.


  3. From Project Explorer, select the Event Log.


  4. From the Analyzer menu, select Export Events and save the file.


  5. Open the exported file in Excel and swap the first two columns, Source and Event. Save the file under a different name.


  6. Add a new Event Log to the project by selecting Add Item from the Project menu. Select New and click Event Log.


  7. Select the new Event Log in Project Explorer. From the Analyzer menu, select Import Events. Select the csv file saved from Excel.


  8. Compare the Event fields of the two Event Logs.



REFERENCES

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

Q242298 INFO: Valid Filter Fields for Visual Studio Analyzer

Additional query words:

Keywords : kbEEdition kbVisAnalyzer kbVS600bug kbDSupport kbGrpDSTools
Version : WINDOWS:6.0
Platform : WINDOWS
Issue type : kbbug


Last Reviewed: January 21, 2000
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.