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
Copy file name to clipboardExpand all lines: README.md
+8-13Lines changed: 8 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,9 +13,9 @@ Welcome to the C# extension for Visual Studio Code! This preview provides the fo
13
13
14
14
The C# extension is powered by [OmniSharp](https://github.com/OmniSharp/omnisharp-roslyn).
15
15
16
-
### **Important!** Breaking Changes as of 1.0.10
16
+
### **Important!** Breaking Changes as of 1.2
17
17
18
-
* The C# extension now only supports [.NET Core RC2](https://blogs.msdn.microsoft.com/dotnet/2016/05/16/announcing-net-core-rc2/). It no longer supports .NET Core RC1 or ASP .NET 5 RC1.
18
+
* The C# extension now only supports .NET Core 1.0. Please upgrade any RC1 or RC2 projects to the 1.0.0 release build.
19
19
***Support for .csproj projects is partially functional on OS X and Linux.** This will impact anyone doing .csproj development on OS X or Linux (e.g. Unity, Xamarin, etc.). We are working to address this in the near future. However, for now, you can use the [Legacy C# Support extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode.omnisharp).
20
20
21
21
### Found a Bug?
@@ -24,17 +24,12 @@ Please file any issues at https://github.com/OmniSharp/omnisharp-vscode/issues.
24
24
### Debugging
25
25
The C# extension now supports basic debugging capabilities! See http://aka.ms/vscclrdebugger for details.
26
26
27
-
### What's new in C# extension version 1.1
28
-
29
-
* Preliminary support for `dotnet test`
30
-
* Fix for OmniSharp installation problems on networks with an http proxy
31
-
* Debugger support for an external console
32
-
* Debugger support for environment variables
33
-
* Support for debugging .NET Core 1.0.0 post RC2 builds
34
-
* Automatic web vs. console debugger configuration detection
35
-
* Detach support
36
-
* Fix expression evaluation errors when referencing assemblies which aren't currently loaded
37
-
* Fix expression evaluation on Windows 7
27
+
### What's new in C# extension version 1.2
28
+
29
+
* Adds debugger support for new Linux versions: Ubuntu 16.04, Fedora 23, openSUSE 13.2, and Oracle Linux 7.1
30
+
* Enhanced debug console output: module loads are now output, and there are launch.json options for controlling what is output
31
+
* Source file checksum support for breakpoints. This ensures that the debugger only sets breakpoints in code that exactly matches the open document.
32
+
* Support for editing the value of variables in the watch and locals window (requires VS Code 1.3)
Copy file name to clipboardExpand all lines: debugger.md
+11-5Lines changed: 11 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ This page gives you detailed instructions on how to debug code running under .NE
5
5
File bugs and feature requests [here](https://github.com/OmniSharp/omnisharp-vscode/issues) and [join our insiders group](http://landinghub.visualstudio.com/dotnetcoreinsiders) to help us build great tooling for .NET Core.
6
6
7
7
####Requirements
8
-
* Requires .NET Core RC2 (will not work with earlier versions)
8
+
* Requires .NET Core 1.0 RC2 or newer (will not work with earlier versions)
9
9
* X64 only
10
10
* Supports OSX, Ubuntu 14.04, Red Hat Enterprise Linux 7.2, Debian 8.2, Centos 7.1, and Windows 7+
11
11
@@ -26,7 +26,7 @@ Install the .NET Core command line tools (CLI) by following the installation par
26
26
##### 3: Install C# Extension for VS Code
27
27
Open the command palette in VS Code (F1) and type "ext install C#" to trigger the installation of the extension. VS Code will show a message that the extension has been installed and it will restart.
28
28
29
-
If you have previously installed the C# extension, make sure that you have version 1.0.0-rc2 or newer. You can check this by opening the command palette (F1) and running 'Extensions: Show Installed Extensions'.
29
+
If you have previously installed the C# extension, make sure that you have version 1.1.6 or newer. You can check this by opening the command palette (F1) and running 'Extensions: Show Installed Extensions'.
30
30
31
31
##### 4: Wait for download of platform-specific files
32
32
The first time that C# code is opened in VS Code, the extension will download the platform-specific files needed for debugging and editing. Debugging and editor features will not work until these steps finish.
@@ -49,20 +49,22 @@ You can also find some example projects on https://github.com/aspnet/cli-samples
49
49
##### 2: Open the directory in VS Code
50
50
Go to File->Open and open the directory in Visual Studio Code. If this is the first time that the C# extension has been activated, it will now download additional platform-specific dependencies.
51
51
52
-
**Troubleshooting 'Error while installing .NET Core Debugger':** If the debugger is failing to download its platform-specific dependencies, first verify that you have the RC2 build of the .NET CLI installed, and it is functioning. You can check this by starting a bash/command prompt and running 'dotnet --info'.
52
+
**Troubleshooting 'Error while installing .NET Core Debugger':** If the debugger is failing to download its platform-specific dependencies, first verify that you have the 1.0.0-preview1-002702 or newer build of the .NET CLI installed, and it is functioning. You can check this by starting a bash/command prompt and running 'dotnet --info'.
53
53
54
54
If the CLI is installed, here are a few additional suggestions:
55
55
56
-
* If clicking on 'View Log' doesn't show a log this means that running the 'dotnet --info' command failed. If it succeeds in bash/command prompt, but fails from VS Code, this likely means that your computer once had an older build of .NET CLI installed, and there are still remnants of it which cause VS Code and other processes besides bash to use the older version instead of the current version. You can try to clean your computer using the uninstall suggestions from http://dotnet.github.io/getting-started/.
56
+
* If clicking on 'View Log' doesn't show a log this means that running the 'dotnet --info' command failed. If it succeeds in bash/command prompt, but fails from VS Code, this likely means that your computer once had an older build of .NET CLI installed, and there are still remnants of it which cause VS Code and other processes besides bash to use the older version instead of the current version. You can resolve this issue by uninstalling the .NET Core CLI, and reinstalling the version you want (see below for macOS).
57
57
* If 'dotnet restore' is failing, make sure you have an internet connection to nuget.org, and make sure that if additional NuGet.Config files are being used, they have valid content. The log will indicate what NuGet.Config files were used. Try removing the files other than the one coming from the extension itself.
58
58
59
+
MacOS .NET CLI Reinstall Instructions: macOS doesn't have uninstall for pkg files (see [known issue](https://github.com/dotnet/core/blob/master/cli/known-issues.md#uninstallingreinstalling-the-pkg-on-os-x)), one option is to remove the dotnet cli directory with `sudo rm -rf /usr/local/share/dotnet` and then install the pkg again.
60
+
59
61
##### 3: Add VS Code configuration files to the workspace
60
62
VS Code needs to be configured so it understands how to build your project and debug it. For this there are two files which need to be added -- .vscode/tasks.json and .vscode/launch.json.
61
63
62
64
* Tasks.json is used to configure what command line command is executed to build your project, and launch.json configures the type of debugger you want to use, and what program should be run under that debugger.
63
65
* Launch.json configures VS Code to run the build task from tasks.json so that your program is automatically up-to-date each time you go to debug it.
64
66
65
-
If you open the folder containing your project.json, the C# extension can automatically generate these files for you. When you open a project and the C# extension is installed, you should see the following prompt in VS Code:
67
+
If you open the folder containing your project.json, the C# extension can automatically generate these files for you if you have a basic project. When you open a project and the C# extension is installed, you should see the following prompt in VS Code:
66
68
67
69
68
70
@@ -134,3 +136,7 @@ Environment variables may be passed to your program using this schema:
134
136
The target process can optionally launch into a seperate console window. You will want this if your console app takes console input (ex: Console.ReadLine). This can be enabled with:
135
137
136
138
"externalConsole": true
139
+
140
+
#### Docker Support
141
+
142
+
Using Visual Studio Code and the C# extension it is also possible to debug your code running in a [Docker container](https://en.wikipedia.org/wiki/Docker_(software)). To do so, follow instructions to install and run [yo docker](https://github.com/Microsoft/generator-docker#generator-docker). This will add files to your project to build a container, and it will add a new debug launch configuration which will invoke a container build, and then debug your app in the container.
"description": "Optional flag to require current source code to match the pdb.",
300
309
"default": true
301
310
},
311
+
"logging": {
312
+
"type": "object",
313
+
"required": [],
314
+
"default": {},
315
+
"description": "Optional flags to determine what types of messages should be logged to the output window.",
316
+
"properties": {
317
+
"exceptions": {
318
+
"type": "boolean",
319
+
"description": "Optional flag to determine whether exception messages should be logged to the output window.",
320
+
"default": true
321
+
},
322
+
"moduleLoad": {
323
+
"type": "boolean",
324
+
"description": "Optional flag to determine whether module load events should be logged to the output window.",
325
+
"default": true
326
+
},
327
+
"programOutput": {
328
+
"type": "boolean",
329
+
"description": "Optional flag to determine whether program output should be logged to the output window when not using an external console.",
330
+
"default": true
331
+
},
332
+
"engineLogging": {
333
+
"type": "boolean",
334
+
"description": "Optional flag to determine whether diagnostic engine logs should be logged to the output window.",
335
+
"default": false
336
+
},
337
+
"trace": {
338
+
"type": "boolean",
339
+
"description": "Optional flag to determine whether diagnostic adapter command tracing should be logged to the output window.",
340
+
"default": false
341
+
},
342
+
"traceResponse": {
343
+
"type": "boolean",
344
+
"description": "Optional flag to determine whether diagnostic adapter command and response tracing should be logged to the output window.",
345
+
"default": false
346
+
}
347
+
}
348
+
},
302
349
"pipeTransport": {
303
350
"type": "object",
304
351
"description": "When present, this tells the debugger to connect to a remote computer using another executable as a pipe that will relay standard input/output between VS Code and the .NET Core debugger backend executable (clrdbg).",
@@ -472,12 +519,50 @@
472
519
"items": {
473
520
"type": "string"
474
521
},
522
+
"default": []
523
+
},
475
524
"requireExactSource": {
476
525
"type": "boolean",
477
526
"description": "Optional flag to require current source code to match the pdb.",
478
527
"default": true
479
528
},
480
-
"default": []
529
+
"logging": {
530
+
"type": "object",
531
+
"required": [],
532
+
"default": {},
533
+
"description": "Optional flags to determine what types of messages should be logged to the output window.",
534
+
"properties": {
535
+
"exceptions": {
536
+
"type": "boolean",
537
+
"description": "Optional flag to determine whether exception messages should be logged to the output window.",
538
+
"default": true
539
+
},
540
+
"moduleLoad": {
541
+
"type": "boolean",
542
+
"description": "Optional flag to determine whether module load events should be logged to the output window.",
543
+
"default": true
544
+
},
545
+
"programOutput": {
546
+
"type": "boolean",
547
+
"description": "Optional flag to determine whether program output should be logged to the output window when not using an external console.",
548
+
"default": true
549
+
},
550
+
"engineLogging": {
551
+
"type": "boolean",
552
+
"description": "Optional flag to determine whether diagnostic engine logs should be logged to the output window.",
553
+
"default": false
554
+
},
555
+
"trace": {
556
+
"type": "boolean",
557
+
"description": "Optional flag to determine whether diagnostic adapter command tracing should be logged to the output window.",
558
+
"default": false
559
+
},
560
+
"traceResponse": {
561
+
"type": "boolean",
562
+
"description": "Optional flag to determine whether diagnostic adapter command and response tracing should be logged to the output window.",
0 commit comments