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.
Refactor analyzer for .NET Standard
See original GitHub issueWe want to be able to build and run the out-of-proc analyzer on .NET Core as well as .NET Standard.
This will likely require separating out interfaces such as the Python registry service and much of the default interpreter implementation.
We could either end up with two assemblies (like Common/VSCommon), or move types into VSInterpreters (though the backwards compatibility implications of this may be more complicated). Alternatively, the builds could produce fundamentally different assemblies between .NET Standard and Core, provided the stdin/out interface is identical (extensions that directly depend on the assembly need to be rebuilt for Core anyway).
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (7 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
The announcement of .NET Standard helps clarify things; basically it’s an API spec that all .NET platforms are expected to implement (.NET Framework and Core included). So basically you code for .NET Standard APIs and you know that it will work whether you’re executing on top of .NET Framework, .NET Core, or Xamarin (as long as those platforms support that version of .NET Standard you’re using).
https://github.com/Microsoft/vscode-python/blob/master/CONTRIBUTING - PYTHON_ANALYSIS.md