Move the extension class and use constant range instead.

Author: bclothier

Rubberduck.Parsing/ComReflection/ComModule.cs

@@ -12,7 +12,7 @@
 using VARDESC = System.Runtime.InteropServices.ComTypes.VARDESC;
 using CALLCONV = System.Runtime.InteropServices.ComTypes.CALLCONV;
 using Rubberduck.VBEditor.ComManagement.TypeLibs.Abstract;
-using Rubberduck.JunkDrawer.Hacks;
+using Rubberduck.VBEditor.ComManagement.TypeLibs.Utility;
 
 namespace Rubberduck.Parsing.ComReflection
 {

Rubberduck.Parsing/VBA/ParseCoordinator.cs

@@ -336,7 +336,7 @@ private void ExecuteCommonParseActivities(IReadOnlyCollection<QualifiedModuleNam
 
         //TODO: Remove the conditional compilation after loading from typelibs actually works.
         //TODO: Improve the handling to avoid host crashing. See https://github.com/rubberduck-vba/Rubberduck/issues/5217
-        [Conditional("LOAD_USER_COM_PROJECTS")]
+        // [Conditional("LOAD_USER_COM_PROJECTS")]
         private void ProcessUserComProjects(ref CancellationToken token, ref IReadOnlyCollection<QualifiedModuleName> toParse, ref HashSet<QualifiedModuleName> toReresolveReferences, ref IReadOnlyCollection<string> newProjectIds)
         {
             RefreshUserComProjects(toParse, newProjectIds);

Rubberduck.VBEEditor/ComManagement/TypeLibs/TypeInfoConstantsCollection.cs

@@ -1,8 +1,8 @@
 using System.Collections.Generic;
 using System.Runtime.InteropServices.ComTypes;
-using Rubberduck.JunkDrawer.Hacks;
 using Rubberduck.VBEditor.ComManagement.TypeLibs.Abstract;
 using Rubberduck.VBEditor.ComManagement.TypeLibs.Unmanaged;
+using Rubberduck.VBEditor.ComManagement.TypeLibs.Utility;
 using TYPEATTR = System.Runtime.InteropServices.ComTypes.TYPEATTR;
 using VARDESC = System.Runtime.InteropServices.ComTypes.VARDESC;
 

Rubberduck.JunkDrawer/Hacks/VarDescExtensions.cs renamed to Rubberduck.VBEEditor/ComManagement/TypeLibs/Utility/VarDescExtensions.cs

@@ -16,13 +16,23 @@ public static class VarDescExtensions
         /// 
         /// There is a small but non-zero chance that there might be a valid pointer that happens to be only in high half of the address...
         /// in that case, it'll be wrong but since VBA is always writing <see cref="VARKIND.VAR_STATIC"/> to the <see cref="VARDESC.varkind"/>
-        /// field, we're kind of stuck...
+        /// field. To accommodate this unlikely possibility, we take advantage of VBA's other failure to comply with MS-OAUT specifications:
+        /// None of its constants has a valid member ID. Normally they are assigned <c>MEMBER_NIL</c> which makes them useless for enumeration. To
+        /// accommodate this, the TypeInfoWrapper in Rubberduck.VBEditor project will generate unique member IDs for those constants. Thus, we can use
+        /// the same range to infer that it's a constant assigned by the TypeInfoWrapper.
         /// </remarks>
         /// <param name="varDesc">The <see cref="VARDESC"/> from a VBA <see cref="ITypeInfo"/></param>
         /// <returns>True if this is most likely a constant. False when it's definitely not.</returns>
         public static bool IsValidVBAConstant(this VARDESC varDesc)
         {
-            return varDesc.varkind == VARKIND.VAR_STATIC && varDesc.desc.oInst != 0;
+            // TODO: Move the function to a better home and avoid duplication of constants (see TypeInfoWrapper)
+            const int _ourConstantsDispatchMemberIDRangeStart = unchecked((int)0xFEDC0000);
+            const int _ourConstantsDispatchMemberIDRangeBitmaskCheck = unchecked((int)0xFFFF0000);
+            const int _ourConstantsDispatchMemberIDIndexBitmask = unchecked((int)0x0000FFFF);
+            if ((varDesc.memid & _ourConstantsDispatchMemberIDRangeBitmaskCheck) >= _ourConstantsDispatchMemberIDRangeStart)
+            {
+                return varDesc.varkind == VARKIND.VAR_STATIC && varDesc.desc.lpvarValue != 0;
+            }
         }
     }
 }