How does it work?

MagNumDB is a database that contains about 350,000 items. These items are constants, names, values all extracted from more than 6,000 header files (.h, .hxx, .hpp, .idl, etc.) provided by standard Windows and Visual Studio SDKs and WDKs.

Some values have been extracted from the very special uuid.lib file that contains the value of thousands of guids and property keys, not present anywhere else in header files. This can explain some duplicates (because names in uuid.lib are not always exactly the same as names in .h parsed files...).

It also contains around 36,0000 undocumented guids that we found ... meeeeep ...


To build this database, we have tried many existing parsers, things like CLANG or other fine tools, but they just don't suit our needs. They can't handle thousands of files that don't compile together, they can't handle some specific (or just very old) Microsoft constructs or annotations, they don't remember the stack of #define directives that led to a definition, they only give you a final AST, not a partial one, etc.

So, in the end, we have written a C/C++ parser named C2P5 (for C/CPP/PreProcessor/Parser), tailored specifically for computing constants. C2P5 is capable of preprocessing, parsing and partially evaluating all header files as if they were included in a one big virtual project (that of course, does not compile) on a 32G RAM machine. It currently supports the following preprocessor and C/C++ constructs:

  • #define preprocessor that define constants
  • #define preprocessor that define expression to compute constants
  • C and C++ constants, strings and enum definitions, and some level of pointerness
  • Special GUID constructs like DECLSPEC_UUID, DEFINE_GUIDSTRUCT, MIDL_INTERFACE, you name it
  • PROPERTYKEY constructs
  • Some IDL constructs
  • Etc.

The parser remembers dynamic preprocessor definitions (#if, #ifdef, etc.) that are conditions for constants definitions and expression computation. All parsed items are saved in the database, as well as the associated conditions. There may be more than one item corresponding to a given name, if there are differences in their associated conditions stack.

C2P5 supports the following types of constants, regardless of the way they are defined in source files:

  • integer, signed or unsigned, from 8-bit to 128-bit
  • floating point number, single (32-bit) or double (64-bit)
  • globally unique identifier, or guid, uuid, CLSID, IID, etc.
  • string, in narrow, wide, or utf-8/16/32 formats
  • character, in narrow, wide, or utf-8/16/32 formats
  • pointer, a constant cast as a pointer
  • property key, or PROPERTYKEY, or PKEY, a combination of a guid (fmtid) and a 32-bit integer (id).

 Powered by

C2P5 and this MagNumDB web site are written in C# and use a Lucene database as a full-text search engine. C2P5 uses a custom ANTLR4cs C grammar for expression parsing, not for preprocessor parsing.


 Frequently Asked Questions

  • Q: Can I run custom queries?
    A: Yes. You can use Lucene's query syntax. Note the Database is case insensitive. Check out the list of columns with their corresponding database column names:

    • Index: the item's index.
    • Name: the item's name, or title. For enum values, it's prefixed with the enum's name.
      Corresponding database field: title.
    • Type: the item's type, expressed in a specific, universal system.
      Corresponding database's field: valuetype, but use the value of the Storage type column for queries on items type.
    • Value: the item's value. For string values, it's displayed as is w/o quotes nor escaping.
      Corresponding database field: value. There is also a typedvalue field that can contain database's Int32, Int64, Float, Double or String typed values.
    • Hex Value: the item's hexadecimal value, only valid for integer types.
      There is no corresponding database field.
    • Signed Value: the item's signed value, only valid for integer and double types. Useful when you found a unsigned number and want to get the corresponding signed value (uint -> int for example).
      There is no corresponding database field.
    • Source lines(s): the source lines from which the item was extracted. Comments and characters such as TAB, CR are preserved.
      Corresponding database field: source.
    • File path: the file path from which the item was extracted, terminated by the line index.
      Corresponding database field: filepath. There are also directory and filename fields. filename is useful to query for values in a given file.
    • Score: Database's score value. Items are returned sorted by score.
    • Guid formats: a utility columns that proposes all possible guid formats. Only valid for guid types.
      There is no corresponding database field
    • Char type: the character encoding (narrow, wide, etc.). Only valid for char and string values.
      Corresponding database field: chartype.
    • Storage type: the exact storage type in the database. Only used for specific queries.
      Corresponding database field: valuetype.
    • Conditions: the list of preprocessor conditions for a given item. If a condition is surrounded with a REVERSE function, it means the reverse condition of what's surrounded was the condition.
      Corresponding database field: conditions. There may be multiple conditions fields for one item.

    Some important points to note:

    • If you search for a negative number (like error codes expressed using signed integers), you can surround the search with double quotes, for example searching for "-2147009290" is equivalent to searching for 0x80073CF6, 80073CF6 (or even 3CF6 in this specific case). If you don't surround negative numbers with double quotes, the system will search for signed and unsigned corresponding values.
    • The full-text search uses items' name, value, hex value, guid formats, source lines, etc. so refine your search if you get back too many items.
    • You can search for guid binary values using just a part of their full definition. For example, if you search for '79eac9c5', it will get you 3 guid entries
    • Leading wild card search (*whatever) is allowed, but it may slow down the search significantly.

    Here are some example or custom queries:

    title:wm_user returns the WM_USER Windows message item, not all items that reference the WM_USER token.

    title:wm_u* returns all items (Windows messages probably) whose name starts with WM_U*.

    value:1024 AND title:wm_* returns all items (Windows messages probably) whose name starts with WM_U* and value is 1024. Note AND must be UPPERCASE for database to understand it as an AND operator.

    value:"00000002-0000-0000-C000-000000000046" returns the IMalloc IID guid value.

  • Q: I always get back 400 items at most. Why?
    A: The MagNumDb site currently limits the number of returned items to this value by design. This should be enough for most real search scenarios (like enums with a big list of values).

  • Q: Some values are empty. Why?
    A: The expression evaluator cannot always compute the final value, because it sometimes require contextual information (custom defines, compiler architecture, etc.) that the parser doesn't have at parsing time. You can enable the Source line(s) column to check what's the corresponding source and try to work it out by yourself. The origin file path and line number is also included.

  • Q: Can I get all values for a given enum?
    A: Sure. For example, __VSHPROPID is the name of an enum, and a query like this: parent:__VSHPROPID will get all the enum's values (66 entries).

  • Q: I sometimes get back items whose name starts with "__magnumdb__enum_". Why?
    A: C allows unnamed enums. The MagNumDb parser just gives them a name, using the defining file name and a counter.

  • Q: I sometimes get back the same item/name twice or more with different values. For example:  TARGET_IS_NT60_OR_LATER. Why?
    A: This can be the case with defines. Their value may be different if they were surrounded by # directives (#if, #else, etc.) in the original source code. You can enable the Condition(s) column to check what are the corresponding conditions for a given item.
    Note: if a condition is surrounded with a funny REVERSE function token, it means the reverse condition of what's surrounded.

 Database Metrics

  • Last update date: Thursday May 13, 2020
  • Items count: 340878
  • Parsed files count: 8447
  • Windows SDK version: 10.0.19041.0
  • NetFx SDK version: 4.8
  • MSVC Tools version: 14.25.28610

 Rest API

There is a JSON version API (you will have to figure out the schema, it's pretty obvious) that you can call here (the search query is the 'q' parameter):

Note this API also has a 400 items maximum limit and the server is monitored for excessive usage (the key can be removed without notice). If you want to get a key, send us an email.



We welcome feedback.
Seen anything missing? A bug? A wrong value? Do you have any suggestion for improvements? Do you have an idea for a cool new feature?

Please contact us here

 About MagNumDB

MagNumDB  2017-2021 Simon Mourier V1.3.2. All rights reserved.

Profile for Simon Mourier at Stack Overflow, Q&A for professional and enthusiast programmers

All product names, logos, and brands are property of their respective owners. All company, product and service names used in this website are for identification purposes only.

All values, names, source code fragments displayed here have been extracted from files that are property of their respective owners.


Index Score Name Type Value Hex value Signed value Guid formats Char type Storage type Source line(s) File path Condition(s)
Index Score Name Type Value Hex value Signed value Guid formats Char type Storage type Source line(s) File path Condition(s)
1 10.18393 __VSSPROPID::VSSPROPID_LAST Int32 -9000 0xFFFFDCD8 -9000 System.Int32
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14549,0)
2 10.18393 __VSSPROPID::VSSPROPID_StartupDir Int32 -9000 0xFFFFDCD8 -9000 System.Int32
VSSPROPID_StartupDir	= -9000,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14550,0)
3 10.18393 __VSSPROPID::VSSPROPID_MDIState Int32 -9001 0xFFFFDCD7 -9001 System.Int32
VSSPROPID_MDIState	= -9001,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14551,0)
4 10.18393 __VSSPROPID::VSSPROPID_VirtualRegistryRoot Int32 -9002 0xFFFFDCD6 -9002 System.Int32
VSSPROPID_VirtualRegistryRoot	= -9002,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14552,0)
5 10.18393 __VSSPROPID::VSSPROPID_OpenFileFilter Int32 -9003 0xFFFFDCD5 -9003 System.Int32
VSSPROPID_OpenFileFilter	= -9003,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14553,0)
6 10.18393 __VSSPROPID::VSSPROPID_FindInFilesFilter Int32 -9004 0xFFFFDCD4 -9004 System.Int32
VSSPROPID_FindInFilesFilter	= -9004,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14554,0)
7 10.18393 __VSSPROPID::VSSPROPID_AddExistItemFilter Int32 -9005 0xFFFFDCD3 -9005 System.Int32
VSSPROPID_AddExistItemFilter	= -9005,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14555,0)
8 10.18393 __VSSPROPID::VSSPROPID_IsInOfficeMode Int32 -9006 0xFFFFDCD2 -9006 System.Int32
VSSPROPID_IsInOfficeMode	= -9006,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14556,0)
9 10.18393 __VSSPROPID::VSSPROPID_InstallDirectory Int32 -9007 0xFFFFDCD1 -9007 System.Int32
VSSPROPID_InstallDirectory	= -9007,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14557,0)
10 10.18393 __VSSPROPID::VSSPROPID_PreBuildRunPreview Int32 -9008 0xFFFFDCD0 -9008 System.Int32
VSSPROPID_PreBuildRunPreview	= -9008,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14558,0)
11 10.18393 __VSSPROPID::VSSPROPID_IsComplexScriptAvail Int32 -9009 0xFFFFDCCF -9009 System.Int32
VSSPROPID_IsComplexScriptAvail	= -9009,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14559,0)
12 10.18393 __VSSPROPID::VSSPROPID_hinstComplexScript Int32 -9010 0xFFFFDCCE -9010 System.Int32
VSSPROPID_hinstComplexScript	= -9010,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14560,0)
13 10.18393 __VSSPROPID::VSSPROPID_hinstMSO Int32 -9011 0xFFFFDCCD -9011 System.Int32
VSSPROPID_hinstMSO	= -9011,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14561,0)
14 10.18393 __VSSPROPID::VSSPROPID_ViewSourceMode Int32 -9012 0xFFFFDCCC -9012 System.Int32
VSSPROPID_ViewSourceMode	= -9012,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14562,0)
15 10.18393 __VSSPROPID::VSSPROPID_RecordState Int32 -9013 0xFFFFDCCB -9013 System.Int32
VSSPROPID_RecordState	= -9013,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14563,0)
16 10.18393 __VSSPROPID::VSSPROPID_Zombie Int32 -9014 0xFFFFDCCA -9014 System.Int32
VSSPROPID_Zombie	= -9014,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14564,0)
17 10.18393 __VSSPROPID::VSSPROPID_AnimationsOn Int32 -9015 0xFFFFDCC9 -9015 System.Int32
VSSPROPID_AnimationsOn	= -9015,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14565,0)
18 10.18393 __VSSPROPID::VSSPROPID_ProcessingPendingMessageFilterMsg Int32 -9016 0xFFFFDCC8 -9016 System.Int32
VSSPROPID_ProcessingPendingMessageFilterMsg	= -9016,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14566,0)
19 10.18393 __VSSPROPID::VSSPROPID_IsInteractive Int32 -9017 0xFFFFDCC7 -9017 System.Int32
VSSPROPID_IsInteractive	= -9017,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14567,0)
20 10.18393 __VSSPROPID::VSSPROPID_DetectFileChanges Int32 -9018 0xFFFFDCC6 -9018 System.Int32
VSSPROPID_DetectFileChanges	= -9018,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14568,0)
21 10.18393 __VSSPROPID::VSSPROPID_OpenFromCurrDocDir Int32 -9019 0xFFFFDCC5 -9019 System.Int32
VSSPROPID_OpenFromCurrDocDir	= -9019,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14569,0)
22 10.18393 __VSSPROPID::VSSPROPID_ReloadChangedFiles Int32 -9020 0xFFFFDCC4 -9020 System.Int32
VSSPROPID_ReloadChangedFiles	= -9020,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14570,0)
23 10.18393 __VSSPROPID::VSSPROPID_AppDataDir Int32 -9021 0xFFFFDCC3 -9021 System.Int32
VSSPROPID_AppDataDir	= -9021,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14571,0)
24 10.18393 __VSSPROPID::VSSPROPID_IsInCommandLineMode Int32 -9022 0xFFFFDCC2 -9022 System.Int32
VSSPROPID_IsInCommandLineMode	= -9022,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14572,0)
25 10.18393 __VSSPROPID::VSSPROPID_ShowOutputPaneOnBuildBegin Int32 -9023 0xFFFFDCC1 -9023 System.Int32
VSSPROPID_ShowOutputPaneOnBuildBegin	= -9023,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14573,0)
26 10.18393 __VSSPROPID::VSSPROPID_ShowTasklistOnBuildEnd Int32 -9024 0xFFFFDCC0 -9024 System.Int32
VSSPROPID_ShowTasklistOnBuildEnd	= -9024,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14574,0)
27 10.18393 __VSSPROPID::VSSPROPID_hmsoinstMSO Int32 -9025 0xFFFFDCBF -9025 System.Int32
VSSPROPID_hmsoinstMSO	= -9025,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14575,0)
28 10.18393 __VSSPROPID::VSSPROPID_ShowMiscFilesProject Int32 -9026 0xFFFFDCBE -9026 System.Int32
VSSPROPID_ShowMiscFilesProject	= -9026,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14576,0)
29 10.18393 __VSSPROPID::VSSPROPID_ObjectMgrTypesImgList Int32 -9027 0xFFFFDCBD -9027 System.Int32
VSSPROPID_ObjectMgrTypesImgList	= -9027,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14577,0)
30 10.18393 __VSSPROPID::VSSPROPID_SCCGlyphsImgList Int32 -9028 0xFFFFDCBC -9028 System.Int32
VSSPROPID_SCCGlyphsImgList	= -9028,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14578,0)
31 10.18393 __VSSPROPID::VSSPROPID_SuppressMessageFilterBusyDialog Int32 -9029 0xFFFFDCBB -9029 System.Int32
VSSPROPID_SuppressMessageFilterBusyDialog	= -9029,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14579,0)
32 10.18393 __VSSPROPID::VSSPROPID_VisualStudioProjDir Int32 -9030 0xFFFFDCBA -9030 System.Int32
VSSPROPID_VisualStudioProjDir	= -9030,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14580,0)
33 10.18393 __VSSPROPID::VSSPROPID_PreBuildRunPreviewSaveOpts Int32 -9031 0xFFFFDCB9 -9031 System.Int32
VSSPROPID_PreBuildRunPreviewSaveOpts	= -9031,
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14581,0)
34 10.18393 __VSSPROPID::VSSPROPID_FIRST Int32 -9031 0xFFFFDCB9 -9031 System.Int32
%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Professional\VSSDK\VisualStudioIntegration\Common\Inc\vsshell.h(14582,0)