Docs: Please suggest the Editor to use for the C# code elements. Please consider producing a version of this tutorial to follow inside of VS

[rstannard]

I've just completed following this tutorial and found it very helpful. I would just make the following comments how it could be slightly improved.
1/ please advise the reader that this tutorial is aimed to be followed outside of the Visual Studio 2017 environment.
2/ if (1) is the case then please suggest an editor to use for completing the code in.
I followed the tutorial using a mix of following the command line steps to create the project structure as well as VS2017 for the C# code pieces.
3/ it would be very useful to see a version of this tutorial which shows the steps to follow inside of VS.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: e0063ceb-57ea-f30c-efed-b2a36314ccaa
• Version Independent ID: bd9a321e-2ef2-491d-cd37-2d9c66f90cc9
• Content: Unit testing C# with NUnit and .NET Core
• Content Source: docs/core/testing/unit-testing-with-nunit.md
• Product: dotnet-core
• GitHub Login: @rprouse
• Microsoft Alias: mairaw

[rprouse]

Good suggestions, thanks. You might want to change the title of this issue to something more meaningful since this repo is for all of the .NET Core documentation. I would do it, but I don't have edit rights in this repository.

[rstannard]

Hi Rob, I've just done that now - I hope its not too wordy ? Happy to take a suggestion.

[skylord-a52]

Rather/as well as than using shell commands, which may be confusing to those new to Visual Studio (like myself), I'd recommend including in-GUI ways to do the same thing.

dotnet new -i NUnit3.DotNetNew.Template can be avoided by installing the NUnit VS Packages from the Marketplace within Visual Studio, for example, and adding new solutions and linking references are fairly simple to do from within the Visual Studio UI.

[mairaw]

Thanks for your feedback @rstannard. I'm adding this to our backlog. We usually start the topics with the CLI version since it's cross-platform, but indeed topics using VS would also be useful.

/cc @BillWagner

[leder11011]

I strongly discourage using VS or Code as long as they are not helpful. I suggest .NET core for Linux and the bash CLI in conjunction with gedit, atom, vim or some other Linux editor available.

[Rick-Anderson]

@Thraka recommend closing this issue. VS is fine as the editor. This tutorial is consistent with all the rest of the unit testing tutorials.

Unit testing is generally not the onboarding/most beginning tutorial.

[Thraka]

@mairaw owns this article so I would let her make the call, but I agree. It will all be rewritten anyhow when these get remade.

[StingyJack]

@Rick-Anderson yeah but someone who is skilled with VS and familiar with unit testing cant actually follow these instructions and get a working result. at least not without monkeying and web searching a bit. For example I would never think to choose a console application as the project type, but Nunit seems to need that. The doc page even says

You've built a small library and a set of unit tests for that library

Then again I wouldnt bother typing most of the stuff in these "tutorials" when I can hit 3 or 4 keys in a VS shortcut. It may be a GUI but its still only 3 or 4 keys compared to typing "dotnet ".