Error List Manager – Visual Studio Plugin

Error List Manager (ELM) extension lets you perform extra actions on Visual Studio’s Error List Window.

Visual Studio 2012 and above

Error List Export as HTML PDF EXCEL Email Print from Visual Studio

Visual Studio 2010

Visual Studio Error List Manager By Shemeer

Currently Error List Manger supports below functionalities.

  • Export
    • HTML
    • Excel
    • PDF
  • Email
  • Print

Error List Manager Settings User Interface allows you to customize the export and other options.

From Visual Studio 2012 and bove this settings can be accessed from Tools->Options->Error List Manager

Export Visual Studio Error List HTML EXCEL PDF

Error List Manager’s Export Configuration Section

Email Visual Studio Error List

Error List Manager’s Email Configuration Section

Print Visual Studio Error List

Error List Manager’s Print Configuration Section

This configuration section allows you to change the default export options as per your choice. By using these options you can generate All/Selected Error List Items as an Excel (.xlsx), HTML or PDF.

Supported Excel Table Styles

Different Table Styles are available for Excel Export.

Export Error List as Excel from Visual Studio

Error List Manager’s Export Excel Table Styles

Export Visual Studio's Error List as EXCEL

ELM Export – Sample Excel file.

Supported HTML Templates

Below listed HTML files are generated using different ELM HTML Templates.

Export Visual Studio's Error List as HTML

HTML- Template A1

Export Visual Studio Error List as HTML

HTML – Template B1

Export Error List from Visual Studio

HTML – Template B2

Export Visual Studio's Error List as HTML

HTML – Template C1

Save Error List from Visual Studio Error List Toolwindow

HTML – Template C2

Supported PDF Templates

Export Visual Studio' Error List as PDF

PDF – Template B1


Using this option you can directly send the Error List items as an attchment in Outlook email client. If oulook is already running then make sure that Visual Studio and Outlook runs with same access rights.

Emailing Visual Studio's Error List using ELM

Emailing Visual Studio’s Error List using ELM


This option will send the Error List to the default printer. You can change any default settings from Print settings window as per your requirement.

Printing Visual Studio's Error List using ELM

Printing Visual Studio’s Error List using ELM


Please Share, Suggest, Vote, Comment – Error List Manger

Error List Manager - Additional options to Visual Studio's Error List


Error List Manager for Visual Studio 2010

Error List Manager for Visual Studio 2012 and above

Please let me know your feedback/suggestions. Thank You!

37 thoughts on “Error List Manager – Visual Studio Plugin

  1. Hi,
    one question and one problem to be reported.

    1. Why PDF creation is disabled?

    2. Exporting to HTML in VS2013 and opening the file directly shows an empty IE window. Taking a look at the source (using the IE) results in an empty source viewer window. Exporting afterwards to an Excel file seems to “release” the HTML file and suddenly it has contents, is displayable, but not complete! The last row is incomplete.
    Any chance for a fix?

    Best regards,


    • Hi Martin,

      As of now Error List PDF generation is disabled due to incomplete pdf rendering. Is this functionality is important for you?

      I just replicated the HTML export issue, will update you with the fix in two days.

      Thanks for your comment,


      • The PDF creation is, for me, more important than Excel.
        I need the PDF or HTML creation for document only.

  2. Pingback: Error List Manager 1.1 is available with more export options | Shemeer's World of Programming

  3. Nope, I have updated the latest details directly in this page itself 🙂

    The changes are, added different HTML – Templates, Enabled PDF Export, Updated Settings User Interface and menu visibility.

    Have you got a chance to look at all this things?

  4. Hi, I’m Italian, and often, in error description there is the character «È». can you set the charset=utf-7 coding instead utf-8 to better seeing ascii 128-255? Thank you

  5. Exchanging UTF-8 by the nearly abandoned UTF-7? By default?

    Please not!

    Dear Lucio, UTF-7 won’t solve the problem of invalid displayed chars after the export! Mostly the application displaying the HTML export with invalid chars has a problem!

    Three possibilities eventually solving the problem:
    1. always using a detected system encoding like ISO 8859-1, so the displaying application oxygen use the save as default.
    2. allowing the user to configure an export encoding.
    3. Convert all characters >= 128 to HTML entities.

    Since I’m on vacation I can’t verify the meta data in a saved HTML file, if the file describes itself to have an UTF-8 encoding.
    If not possibilities 1 and 2 may help, or to add the meta tag write the charset declaration.

  6. Sorry, Ok, I’m not an HTML and encoding expert. I saw that utf7 for me was well. Now I saw also Iso8859-1 is well for me.
    Yes, the HTML file describes the encoding into a meta data. I throw also to delete it, and the browser shows the HTML file well.

    Thank you!

    • Eventually there is a deeper problem!

      The most common encoding in western Europe is ISO 8859-1/15. Our computers are mostly configured to use CP1252, and the must common and most universal (internet) encoding is UTF-8.

      If the exported HTML file correctly specifies the UTF-8 encoding in its head in the meta data, and if diacritics are displayed wrongly, but only not using the default browser encoding fallback ISO 8859-1, than because those diacritics are not stored as UTF-8 characters, not using the correct two byte sequences! If they get displayed correctly with a HTML file with a deleted encoding specification, than because the fallback encoding set in the browser, in Italy ISO8859-1, is used, because they are not UTF-8 encoded!

      So the error list manager doesn’t seem to change the encoding of the strings got from visual studio which should have CP1252 encoding, which is mostly identical with ISO8859-1. Since the HTML file declares to be written using UTF-8 encoding, the strings extracted from the error list must get re-encoded to UTF-8 before they get written to the HTML file! Or the specified encoding in the exported HTML file must match the system encoding – in western Europe mostly CP1252!

      But, since I’m on vacation, without access to an ELM installation, this is pure theory!

      Btw exporting to a pdf file might be influenced by the encoding-hell as well!

      Best regards,

      Martin with greetings from the alps in Bavaria

  7. Pingback: Error List Manager 2 Released with Visual Studio 2015 support – Shemeer's World of Programming

  8. Source HTML is not encoded when selecting to Export to HTML, therefore the report can include input boxes and other HTML elements instead of the offending HTML source.

  9. Will this allow me to export more than the 200 row limit (for the error list) in Visual Studio 2012? Do I need to have a solution open to install this? I don’t want to add it to the source permanently. Also, I was getting and issue with the install asking for MPF 12.0

    • It should work for any number of rows present in error list. You can install this without opening Visual Studio also, If you’re still facing the issue, please share the error screenshot for checking

  10. First, thanks for doing this as I can’t believe it’s not part of the IDE by default!

    The one thing I would improve is to include the “Code” column from the error list, including the hyperlink. This would be especially helpful to sort the resulting spreadsheet by in order to group the items by Error/Warning code since the Description column injects variable names.

    Use case: Performing Code Analysis. Sort by code to determine how many “issues” are found for each rule. Hyperlinks destinations for code analysis are actually good to help solve the issue.

  11. Feature Request: When there are no results the export buttons are disabled. Having no results is still something we’d like to know about (its good thing right)

  12. Feature Reqest: It would really really reeeeally great if the export could be automated. For example, after a build, the plugin could be configured to export to a predefined file.

  13. Hi,
    First I’ll say thanks for this amazing VS extension.
    I wanted to know if I can excess it through a .cs file because I want the process to be automatic.
    And if yes then how could we do that ?

  14. Hi Shemeerns,

    This is one great useful plugin.
    Unfortunately with newer versions of Visual studio (tested with VS 2019 enterprise) it triggers an annoying warning saying One or more extensions were loaded with a deprecated API. There is also an additional error when you load it first time.
    Any chance for an update any time soon?
    Ilie C.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s