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
David Fowler c45ff35aed Successful build on OS X and linux
- Mono 4.3 was required to work with certain compilation options on the
first pass but this is temporary.
- Support outputting portable pdbs when not running on windows by
default
2015-10-18 07:10:22 -07:00
ext/CLRHost ubuntu packaging 2015-10-16 15:57:59 -07:00
package_tool Code review feedback, normalize whitespace to spaces 2015-10-16 12:13:52 -07:00
scripts Bootstrapping on OSX and Linux require mono (mcs specifically) 2015-10-18 04:02:58 -07:00
src Successful build on OS X and linux 2015-10-18 07:10:22 -07:00
test/TestApp fix TestApp project.json 2015-10-15 15:34:14 -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 undo gitignore changes 2015-10-16 12:15:25 -07:00
build.cmd port DNX's ApplicationHostContext as ProjectContext 2015-10-14 15:37:39 -07:00
build.sh Assign execute privilege on build.sh 2015-10-08 16:56:15 -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 port DNX's ApplicationHostContext as ProjectContext 2015-10-14 15:37:39 -07:00
Microsoft.DotNet.Cli.sln Changes to dotnet-compile 2015-10-18 01:17:13 -07:00
netci.groovy Execute build.sh from current directory. 2015-10-08 16:27:22 -07:00
NuGet.Config Closer to xplat build working 2015-10-18 06:53:47 -07:00
NuGet.master.config add readme 2015-10-08 14:41:04 -07:00
README.md Update README.md 2015-10-08 15:34:41 -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