Add pointer for .NET debugging for Rider #5924
Conversation
briandealwis
added
the
docs-modifications
|
Please visit http://35.235.96.90:1313 to view changes to the docs. |
container-tools-bot
removed
the
docs-modifications
|
Error creating deployment, please see controller logs for details. |
1 similar comment
|
Error creating deployment, please see controller logs for details. |
| {{< /alert >}} | ||
|
|
||
| {{< alert title="JetBrains Rider" >}} | ||
| This set up does not yet work with JetBrains' Rider, |
There was a problem hiding this comment.
does not yet work [automatically | out of the box] with JetBrains Rider ?
There was a problem hiding this comment.
as discussed on chat:
does not yet work automatically with Cloud Code for IntelliJ in JetBrains Rider
is even clearer
Codecov Report
@@ Coverage Diff @@
## master #5924 +/- ##
==========================================
- Coverage 70.90% 70.90% -0.01%
==========================================
Files 448 449 +1
Lines 16968 16974 +6
==========================================
+ Hits 12032 12035 +3
- Misses 4038 4040 +2
- Partials 898 899 +1
Continue to review full report at Codecov.
|
|
had a tiny suggestion. but LGTM. |
Description
skaffold debug's setup for .NET Core does not work for JetBrains Rider. Add a pointer to Cloud Code for IntelliJ's workaround. The PR also puts the OmniSharp details into a separate call out.