CI to automate build of dotnet tarball for dotnet6-sdk aport https://gitlab.alpinelinux.org/alpine/aports/-/tree/master/community/dotnet6-sdk
Find a file
Andrew Stanton-Nurse 6825aec802 Update README.md
2015-10-08 15:17:08 -07:00
scripts merge my spike on compile/publish/run and switch from PS1 to C# 2015-10-06 10:46:43 -07:00
src add some readme 2015-10-08 14:49:39 -07:00
test/TestApp add some readme 2015-10-08 14:49:39 -07:00
.gitattributes merge my spike on compile/publish/run and switch from PS1 to C# 2015-10-06 10:46:43 -07:00
.gitignore Add gitignore 2015-10-03 11:36:46 -07:00
build.cmd add readme 2015-10-08 14:41:04 -07:00
build.sh add readme 2015-10-08 14:41:04 -07:00
global.json initial spike of compile, publish and run 2015-10-05 21:22:26 -07:00
LICENSE Initial commit 2015-10-02 11:03:16 -07:00
makefile.shade add readme 2015-10-08 14:41:04 -07:00
Microsoft.DotNet.Cli.sln code review feedback and clean-up 2015-10-07 14:39:36 -07:00
NuGet.Config initial spike of compile, publish and run 2015-10-05 21:22:26 -07:00
NuGet.master.config add readme 2015-10-08 14:41:04 -07:00
README.md Update README.md 2015-10-08 15:17:08 -07:00

.NET Command Line Interface

Building/Running

  1. Run build.cmd or build.sh from the root
  2. Use scripts/dotnet to try out the dotnet command.

Notes

Right now the CLI uses DNX as an application host. Eventually it will become self-hosted, but for now that means a few things:

  • Requires VS 2015 with Web Development Tools installed to open in VS
  • Requires that you have a DNX installed (the build script should set it up for you though)
  • Compilation is not required before building, but you must run dnu restore (which comes from the DNX commands) after changing dependencies. If you add/remove dependencies in VS, it will run it for you

A simple test (windows only for now)

Note: The explicit --framework and --runtime switches will definitely be going away :)

  1. cd test\TestApp
  2. ..\..\scripts\dotnet run --framework dnxcore50 --runtime win7-x86