Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
RuntimeEnvironment.GetRuntimeInterfaceAsObject is not supported
See original GitHub issueRunning the Microsoft.DotNet.Analyzers.Compatibility, I found one occurence of API that is not supported on .NET Core.
In ComponentManagerBroker we call RuntimeEnvironment.GetRuntimeInterfaceAsObject. This method throws a PlatformNotSupportedException.
I wasn’t actually capable of writing a repro. This code is hit only in the case where there is a “native component manager” . Since we’re trying to retrieve a IMsoComponentManager, I’m guessing this is specific to hosting scenarios in Microsoft Office.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Fair point… We will reopen for now. I’ll find an office contact to help us test this scenario.
Since Office is not interested into coordinating usage of ComponentManager API (see #1763) I opened #3536 for discussion of alternatives. I prefer removal or disabling of ComponentManager integration since WPF seems to do fine without it. Not starting the discussion here because this issue can be fixed independently before discussion in #3536 yields results, but if consensus is achieved first then of course both issues can be resolved together.