You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will scaffold out the projects in a common layout. Samples should be a single file, with the entrypoint being the command line so that `dotnet run -- [args]` can be used in the docs.
11
+
This will create an initial scaffold for a sample and add it to the solution file.
10
12
11
-
In the future, we expect to set up .editorconfig/stylecop to enforce a shared style across the samples, but for now, the goal is to move the inline samples to this compilable solution.
13
+
## Migrate old samples
14
+
15
+
```powershell
16
+
./migrate-sample.ps1 path-to-md-file
17
+
```
18
+
19
+
This will do an inital extraction and clean up of the file, as well as add the code to the solution. Additional clean up will be necessary, but should be minimal.
12
20
13
21
General changes to move a sample:
14
22
15
23
- Many examples give details on how to open a project; this can be removed
16
24
- Sections about what `Dispose/Close/etc` is can be removed - this is an artifact from before `using` was common
17
25
- Samples currently have a "How the Sample Works" section followed by the actual sample. Going forward, this will be collapsed to just the sample - any comments required will be in the cs/vb
18
-
- Many users use the VB examples, so we will maintain them. Using docfx tabs allows us to hide the languages not needed by a viewer
26
+
- Many users use the VB examples, so we will maintain them. Using docfx tabs allows us to hide the languages not needed by a viewer
27
+
28
+
## Code set up
29
+
30
+
In the future, we expect to set up .editorconfig/stylecop to enforce a shared style across the samples, but for now, the goal is to move the inline samples to this compilable solution.
0 commit comments