Updated the wiki.
Maria Naggaga
Родитель
1b2fa8c479
Коммит
fdffd8f360
4
Home.md
4
Home.md
|
|
@ -50,6 +50,6 @@ Support for 3rd party intergation
|
|||
List of areas we are looking for community support.
|
||||
|
||||
#### Summary
|
||||
Please note these are just examples of what we plan to work on in the next 6 -12 months. We always try our best to keep you up to date and may make changes based on our customer's feedback.
|
||||
These are just examples of what we plan to work on in the next 6 -12 months. We always try our best to keep you up to date and may make changes based on our customer's feedback.
|
||||
|
||||
*Note: If you stumble across this between 2/11/19- 2/21/19 you are looking at the draft.*
|
||||
**Please Note: That the Try .NET tool has had complete overhaul over the past few months. As a result, we will be updating our Wiki and roadmaps to reflect the exciting times we have ahead. Thank you, and please do keep an eye on our repo.**
|
||||
|
|
@ -1,82 +0,0 @@
|
|||
# Product Roadmap Overview
|
||||
|
||||
|
||||
| Icon | Description |
|
||||
| ------------- | ------------- |
|
||||
| Completed | Check mark |
|
||||
| Not Started | No check |
|
||||
| In progress | :hammer: |
|
||||
| Stretch goal | :tophat: |
|
||||
|
||||
## Try .NET Roadmap 2018
|
||||
----------------------------
|
||||
|
||||
In 2017 we did a limited preview of Try .NET on docs.microsoft.com. Try .NET is an inline code runner, and scratchpad that enables people to experiment and learn .NET Core in the browser.
|
||||
|
||||
*Note: Currently Try.NET only supports C#, but we plan to support F# and VB in the near future.*
|
||||
|
||||
As we explore the next iteration of the service, we have created a set of themes that will work towards to provide value to our users.
|
||||
|
||||
|
||||
# Try .NET Themes
|
||||
|
||||
- **Friction-free Exploration**: Try .NET was created to enable users to test and explore .NET core in the browser. In September 2017, we launched the first login-free Try .NET experience across docs.microsoft.com including [quick starts](https://docs.microsoft.com/en-us/dotnet/csharp/quick-starts/) and [reference documentation](https://docs.microsoft.com/en-us/dotnet/api/system.datetime?view=netcore-2.1). Over the course of the year, we will continue to expand these experiences across docs and 3rd party documentation.
|
||||
- **Simple to Embed**: As we grow our customer and user base, we want to enable seamless end to end experiences. It is not only essential for us to create friction-free user experiences but, to allow all .NET content developers to embed Try .NET easily to their documentation, blogs or websites.
|
||||
- **Smooth transition (*Save and work locally*)**: Getting started, exploring and testing with Try .NET is excellent. As a service, we want to enable our users to save their work to smoothly to a repo or storage of their choice or easily open up their code in an editor (e.g. Code or VS).
|
||||
|
||||
# Friction-free Exploration
|
||||
|
||||
From the beginning (September 2017), we have worked to create easy ways for developers to explore and test .NET code in the browser. For example, over the past six months, we have focused on supporting multiple console applications (*see image A and B*).
|
||||
|
||||
|
||||
*Image A*
|
||||
|
||||
*Image B*
|
||||
|
||||
We still have a so much more we are eager to get done. Our community has asked for more .NET Core app support. As Try .NET expands to support more .NET Core applications, you will see a significant focus on the basic developer expectations.
|
||||
|
||||
## Basics
|
||||
|
||||
Users do expect some basic features, with their online developer experiences. The goals of these features are to make the transition to a local editor as comfortable as possible.
|
||||
|
||||
- [x] IntelliSense.
|
||||
- :hammer: GitHub Integration.
|
||||
- [x] Gist Support
|
||||
- [ ] Load .NET Core project repo
|
||||
- [x] Set Custom themes.
|
||||
- [x] Use predefined VS Code themes.
|
||||
- :hammer: Support for .NET Core applications.
|
||||
- [x] Console Application.
|
||||
- :hammer: ASP.NET Core application.
|
||||
- [x] **Basic** multifile support
|
||||
- [ ] Multiple language support.
|
||||
- :hammer: Cross browser support.
|
||||
- [ ] Support for 3rd party libraries.
|
||||
- [ ] Mobile Support - Try .NET working on mobile.
|
||||
|
||||
|
||||
# Simple to Embed
|
||||
We built [Try.NET](https://www.microsoft.com/net/platform/try-dotnet) to enable great experiences for users to easily engage with .NET code in the browser. As we grow, we want to allow content developers to embed [Try .NET](https://www.microsoft.com/net/platform/try-dotnet) content on to their sites easily.
|
||||
- :hammer: Create a sign up process
|
||||
- :hammer: Try .NET API
|
||||
- :hammer: Just an **iframe**: iframes are the heart of our acquisition process. You can see our current embed story [here](https://www.microsoft.com/net/platform/try-dotnet); which we are looking to make easier. Over the course of this year, it is our goal to continue to simplify and improve our embed story.
|
||||
- :hammer: Try .NET documentation: We are committed to creating proper developer documentation. It is essential that our developers have the support they need to get up and running with our services quickly.
|
||||
|
||||
# Smooth Transition (*save and work locally*)
|
||||
Starting or trying out .NET code in the browser is exciting and we are glad that we can support you in your journey. We want to make sure as you continue to write code using Try .NET, that you can easily save your work and open it locally on your machine.
|
||||
|
||||
## Save
|
||||
- [ ] Persistent work: Try .NET uses cases are growing beyond simple console applications. Users in the future will be able to finish a tutorial over time, and as a result, we want to make sure that they can easily save their work.
|
||||
To enable this scenario, we are exploring the ability to save their work to a repo or online file hosting service.
|
||||
- [ ] Save to GitHub
|
||||
- [ ] Save to file hosting service (for example, OneDrive)
|
||||
|
||||
## Work Locally
|
||||
- [ ] It is important to us that you can effortlessly take your code with you from browser to desktop. As a result, we want a user to be able to open their code from a Try .NET to Visual Studio or Code.
|
||||
- :tophat: One click to Visual Studio or Code: Once a user has completed their work using Try .NET it is our goal to provide them with the ability to open in their work in an editor with a click of a button.
|
||||
|
||||
# Summary
|
||||
|
||||
These are examples of the work we will be focusing on to improve the Try .NET experience this year. As you know, plans may shift, and we might make changes to our product roadmap over the year.
|
||||
|
||||
As always, we welcome suggestions and feedback.
|
||||
|
|
@ -1 +0,0 @@
|
|||
Document this page here https://try.dot.net/docs
|
||||
|
|
@ -1,8 +0,0 @@
|
|||
# Techincal Roadmap Overview
|
||||
|
||||
| Icon | Description |
|
||||
| ------------- | ------------- |
|
||||
| In production | :green_book: |
|
||||
| Under review | :orange_book: |
|
||||
| In progress | :hammer: |
|
||||
| blocked | :key: |
|
||||
Загрузка…
Ссылка в новой задаче