Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Properly handle DIA imports #10

Closed
jgefele opened this issue Dec 11, 2015 · 2 comments
Closed

Properly handle DIA imports #10

jgefele opened this issue Dec 11, 2015 · 2 comments
Assignees
@jgefele
Labels
bug

Comments

@jgefele
Copy link
Collaborator

jgefele commented Dec 11, 2015

There are some rare issues with VS2015 update 1 and DIA.
Christian, can you provide the error message please?
@jgefele jgefele added the bug label Dec 11, 2015
@csoltenborn
Copy link
Owner

Error message when executing tests locally:

System.IO.FileNotFoundException: Die COM-Klassenfactory für die Komponente mit CLSID {3BFCEA48-620F-4B6B-81F7-B9AF75454C7D} konnte aufgrund des folgenden Fehlers nicht abgerufen werden: 8007007e Das angegebene Modul wurde nicht gefunden. (Ausnahme von HRESULT: 0x8007007E).

@jgefele
Copy link
Collaborator Author

jgefele commented Dec 28, 2015

Just for the record, with the current build (0.2.2.181) which uses an updated DIA DLL it fails in Visual Studio 2013 with the following message:

An exception occurred while test discoverer 'TestDiscoverer' was loading tests. Exception: Retrieving the COM class factory for component with CLSID {E6756135-1E65-4D17-8576-610761398C3C} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).

@jgefele jgefele mentioned this issue Dec 29, 2015
Closed
@jgefele jgefele self-assigned this Dec 29, 2015
jgefele added a commit that referenced this issue Jan 6, 2016
@jgefele
Add support for different versions of MSDIA (#10)
9a0baeb 
Calls to FinalReleaseComObject were removed intentionally (http://blogs.msdn.com/b/visualstudio/archive/2010/03/01/marshal-releasecomobject-considered-dangerous.aspx)
This also seems to fix strange occurrences of System.Runtime.InteropServices.InvalidComObjectExceptionat the end of debugging a set of Google Test tests.
@jgefele jgefele closed this as completed Jan 7, 2016
csoltenborn pushed a commit that referenced this issue Jul 30, 2017
@rpjohnst
Merge pull request #10 from Microsoft/dev/rujohnst/symbol-map
d376f31 
Store test signatures in a Dictionary
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jgefele jgefele

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@csoltenborn @jgefele