> Originally reported in #5217 -- though this issue was symptomically fixed by restoring the conditional flags, we still need to know why it crashed and there was difficulty in creating a MVCE.

With gratitude to @SteveLaycock for going above and beyond in helping in creating a reproduction, I can verify that this given code will cause an access violation:

```
Private Type foo
bar As Class1
End Type

Private x As foo
```

The crashing happens when we try to resolve the `x` typ

> Both designers individually seem to work but there are issues with loading WinForm designer with WPF element host, because WPF can't find itself, apparently. However, it is verified that runtime does work just fine.

There is still the bogus warning about re-importing SDK because the `Core` and `Main` uses a different SDK than the rest of projects. To handle that, conditions may be needed. and will be investigated.

> **Rubberduck version information**

Version 2.4.1.4901
OS: Microsoft Windows NT 10.0.17763.0, x64
Host Product: Microsoft Office x64
Host Version: 16.0.12026.20334
Host Executable: EXCEL.EXE

**Description**
Sometimes when I am working Rubberduck stops doing refactorings. If I try to rename a class it simply doesn't do anything. The same thing also happens with opportunities such as adding attributes etc. Simply restarting Rubberduck fixes the problem until it appears again, doing a r

> I am at a loss what might be the root cause here. It is expected that every `CodePane` belongs to a `CodeModule` and that it can be obtained via the `CodeModule` property of the code pane object from the interop library.

I guess, we could wrap the request for the `QualifiedModuleName` in `SelectionService.OpenModules` in a try-catch block and log COM exceptions as warnings. That will omit the corresponding components from the returned collection and thus prevent selection recovery for them,

> **Justification**
I have a couple of unit tests where I have to check for floating point equality, and that can sometimes cause some problems. At the moment I have to make a separate function that returns a boolean and then use "IsTrue" instead.

**Description**
Would be great if we could have a separate `AreEqualNumeric` or something like that which checks for value equality taking things like floating point quirks into account. Possibly also allowing optional arguments for setting absolu

> Does anyone know how the union will behave in C#? According to the MS-OAUT, the union will be a different size between 32-bit and 64-bit platforms because of the union between a `ULONG` Windows data type which is 32-bit integer and the `* VARIANT` which is a pointer and thus scales with the platform:

```
typedef struct tagVARDESC {
MEMBERID memid;
LPOLESTR lpstrReserved;
[switch_type(VARKIND), switch_is(varkind)]
union {
[case(VAR_PERINSTANCE, VAR_DISPATCH, VAR_ST

> Addendum: I can confirm that even though the `attrib.cVars` is 0 on 32-bit, the `ITypeInfoWrapper.Vars` does indicate there is one so we do have that information about the `x` field but it's getting skipped over because `cVars` is reported to be zero. Furthermore, the `VARDESC` for the `x` seems to be all in the order; the `lpvarValue` is zero and all other members seems similar to what I'd see on the 64-bit platform.

So, it's simply not happening on 32-bit only because we aren't hitting th

> Ok, the mystery of why `cVars` don't concide on 32-bit/64-bit platform is resolved:

https://github.com/rubberduck-vba/Rubberduck/blob/f606675a9ee8e06474d2b41efcd175882440b812/Rubberduck.VBEEditor/ComManagement/TypeLibs/TypeInfoConstantsCollection.cs#L50

https://github.com/rubberduck-vba/Rubberduck/blob/f606675a9ee8e06474d2b41efcd175882440b812/Rubberduck.VBEEditor/ComManagement/TypeLibs/TypeInfoWrapper.cs#L416-L424

Therefore, it's all down to the fact that on 64-bit platform, the `lpva

Merge pull request #5203 from bclothier/MiscBugFixes

Introduce dockable context menu to toolwindows

> Just as a matter of note - there are few ways to handle the roundings (at least that I know of).

1) Absolute epsilon: `Abs(a - b) < c`.
2) Relative epsilon: `Abs(a/b) < c`
3) Units in the last place: `Abs(ReinterpretAsLngLng(a) - ReinterpretAsLngLng(b)) < c`

Of the 3, the last is difficult to implement in VBA as it does not allow reading the doubles as integers without using API. Each has their advantages and disadvantages, since it can depend on what kind of range one is dealing. For

> **Rubberduck version information**
Version 2.4.1.20197
OS: Microsoft Windows NT 6.1.7601 Service Pack 1, x64
Host Product: Microsoft Office 2013 x86
Host Version: 15.0.5023.1000
Host Executable: EXCEL.EXE

**Description**
Column headers collapse after ignoring or unignoring a unit test. Not a bug per-se, may even be by design but makes it frustrating when doing this multiple times. This ties in to https://github.com/rubberduck-vba/Rubberduck/pull/5064#issuecomment-519775518 and ignorin

> When I look at the AppVeyor build log, at the very bottom, it says:

C:\projects\rubberduck\Rubberduck.Core\UI\Inspections\InspectionResultsControl.xaml(246,14): error MC3015: The attached property 'DataGrid.RowDetailsTemplate' is not defined on 'Grid' or one of its base classes. [C:\projects\rubberduck\Rubberduck.Core\Rubberduck.Core.csproj]

But the solution builds fine for me in Visual Studio. Is there something I need to fix on my end? Was this to do with my `next` branch being out of