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
2015-10-22 12:14:58 -07:00
ext/CLRHost ubuntu packaging 2015-10-16 15:57:59 -07:00
package_tool More cleaning up, consistency 2015-10-22 10:23:47 -07:00
scripts Run Docker Build in Ubuntu CI 2015-10-22 12:14:58 -07:00
src clean things up 2015-10-22 10:20:42 -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 implement bootstrapping without DNX 2015-10-20 17:36:25 -07:00
build.sh implement bootstrapping without DNX 2015-10-20 17:36:25 -07:00
debian_config.json build and fetch results 2015-10-21 23:41:38 -07:00
global.json Initial commit 2015-10-03 11:34:08 -07:00
LICENSE Initial commit 2015-10-02 11:03:16 -07:00
Microsoft.DotNet.Cli.sln Support resx file embedding 2015-10-18 21:07:48 -07:00
netci.groovy Run Docker Build in Ubuntu CI 2015-10-22 12:14:58 -07:00
NuGet.Config Remove corpnet feed 2015-10-20 22:20:56 -07:00
NuGet.master.config add readme 2015-10-08 14:41:04 -07:00
README.md Update README.md 2015-10-21 15:47:45 -07:00

.NET Command Line Interface

Build Status

Ubuntu 14.04 Windows Mac OS X
Debug Build Status Build Status Build Status
Release Build Status Build Status Build Status

Building/Running

  1. Run build.cmd or build.sh from the root
  2. Use artifacts/{os}-{arch}/stage2/dotnet to try out the dotnet command. You can also add artifacts/{os}-{arch}/stage2 to the PATH if you want to run dotnet from anywhere.

Notes

Right now the CLI uses DNX for NuGet restore.

Visual Studio

  • 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

Visual Studio Code

A simple test

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

  1. cd test\TestApp
  2. dotnet publish --framework dnxcore50 --runtime win7-x64