How to try trydotnet console in my learning platform - https://ilovedotnet.org?

[fingers10]

Dear team,

I had a vision couple of years back to give interactive experience using blazor wasm. So I started https://ilovedotnet.org 2-3 years back where I write about topic and give in browser demo using blazor wasm components. Today I came across this awesome dotnet try.

I tried using the iframe url <iframe src="https://try.dot.net/?fromGist=df44833326fcc575e8169fccb9d41fc7"></iframe> mentioned in the official page but not a successful attempt.

I quickly noticed there is something called private preview which is also mentioned in the official page.

Simple to embed
Go beyond copy and paste samples to live snippets. Our private preview customers can embed live .NET code into blogs and documentation.

But not sure where to head from there... I'm not able to find any steps / link to apply for preview. Or if there is any step by step documentation available on how to setup this I would be more happy to try this in https://ilovedotnet.org learning platform.

Please can you folks help me with your expertise on this?

[fingers10]

@dalehhirt and @jonsequitur I saw your commits in this repo. Thank you for maintaining this repo. Now I need your help and expertise here. Please can you assist me on next steps?

[jonsequitur]

Allowing you to host your own Try .NET instances is a long-term goal of the repo but is not currently being worked on. We've moved closer with the latest improvements though. If you're feeling motivated to give the latest changes a try, I'm happy to give pointers.

This Dockerfile would be a good starting point for deployment. The thing I haven't tried yet is customizing the Prebuild instances in the container, for example if you want to add support for additional NuGet packages. (Try .NET doesn't allow restoring and building in the container, for security and performance reasons.)

A good starting point for understanding how the system works might be the developer guide, here: https://github.com/dotnet/try/blob/main/Developer-guide.ipynb

And if you want to understand the whole flow all the way from the browser to the server, this diagram might be helpful (or really confusing): https://github.com/dotnet/interactive/tree/main/src/Microsoft.DotNet.Interactive.CSharpProject#try-net--microsoft-learn-flow