-
-
Notifications
You must be signed in to change notification settings - Fork 354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create .NET Core/Visual Studio Code cross-platform setup instructions #146
Comments
I totally agree! And it is something we are planning on doing, it's just that the .NET Core stuff is still quite a bit in flux. At the moment, Microsoft is working hard to complete the work of reverting he project system to MSBuild (instead of For some more information, see #138. |
I'll keep an eye out for when the xcsharp maintainers feel it's mature enough, I'd be happy to help with the porting process. Thanks! |
@canweriotnow Great! We'll post any updates here. By the way, if you're interested in tracking the work Microsoft is doing, you can check the CLI and MSBuild repositories. |
As a reminder, we will be updating the docs as part of #200. We should be adding docs for the following scenarios:
It might seem a bit much, but I think this will be worthwhile. |
I've updated the .NET Core PR with some initial docs on how to install or run the tests. If anyone would read and check them, that would be great! Here are the direct links to the files: I've opted to not have detailed instructions on how to run the tests in the various IDE's, as most other language tracks also don't do it. It's also much easier for us maintainers if we have a single, supported way to run the tests. In our case, I opted for the .NET CLI option for three reasons:
CC: @canweriotnow @GalaDe @robkeim @balazsbotond @bressain @jmbradnan |
@ErikSchierboom I just had a quick look through the documentation and it looks good! Thanks for all of your work on this. |
@robkeim Thanks! Tomorrow is the Visual Studio 2017 and .NET CLI 1.0 launch. If everything runs fine on those release versions, I'll (finally) merge the .NET Core PR. Would be great to finally have it working. We can then work on further polishing the track. I've actually did some thinking a found lots of ways we can improve things even more. For all of these ideas, I've created a new issue. |
@canweriotnow With #199 merged, I think this issue can now be closed. To be clear, we've updated the track to be based on the .NET CLI, which is cross-platform and thus has the same interface on all platforms. You should thus now have things nicely working on .NET Core! |
Inspired by #38, esp. comments by @NobbZ and @ErikSchierboom -
I'm running .NET Core and Visual Studio Code on Ubuntu and it's a dream. Way nicer for doing exercism exercises than the ceremony and overkill of Visual Studio, and it's easily installed on Windows, OS X, and Linux... https://www.microsoft.com/net/core#linuxubuntu has dead simple instructions and ends with a link to download VS Code...
I think it might be well worth doing a cross-platform howto with a unified workflow, then have Visual Studio / Xamarin as an advanced/alternative option; VS and MonoDevelop are fine for people who are already using them, but with the amount of HALP! requests getting started w/ C# and/or F# on Gitter, streamlining the process with uniform, open-source tools (and without the heavyweight IDEs) seems like a good way to lower the barrier to entry for new users.
The text was updated successfully, but these errors were encountered: