-
Notifications
You must be signed in to change notification settings - Fork 6k
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.
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
Not Terribly Helpful #35269
Comments
Hi @markolbert Can you paste the code you used? It should have worked, and I'm not sure how best to explain what happened. |
It was a static method in a static class:
As I recall, the interactive window complained about not being able to find System.Math. But the basic point of my suggestion is to include one or more examples of using methods defined in an assembly (ideally, which require the need for other assemblies to be loaded, like my case). |
Thanks @markolbert That's a limitation of the interactive implementation, and how it's used on the learn.microsoft.com site. Our goal for the interactive tutorials is to help beginners, or provide very small, focused, samples in API documentation. That led us to limit the assemblies that are loaded. We want to limit the cost of running the deployment, which means limiting which assemblies are loaded. We're looking at long-term solutions such as using polyglot notebooks, where it's easier to enable content authors and users to load assemblies. I'd like your thoughts on those technologies as well. For this issue, we should have a side-bar article that clearly explains the limitations. These include:
|
How about some explanation of using the interactive window with custom methods? When I try to do that, all I get is an unending sequence of error messages saying "The name 'MethodName' does not exist in the current context". Which is amazingly funny, since I right-clicked Execute in Interactive from >>inside<< the source code for the method.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
Associated WorkItem - 400539
The text was updated successfully, but these errors were encountered: