Commit graph

27 commits

Author SHA1 Message Date
Piotr Puszkiewicz
d55a8f8188 Add missing copyright headers to all cs files 2017-03-02 21:04:03 -08:00
Piotr Puszkiewicz
6fcbefa4f7 [WIP] Removes *3 verbs, making msbuild the driver (#4456)
Removes *3 verbs, making msbuild the driver
2016-10-27 18:46:43 -07:00
Livar Cunha
1570e0fde4 Moving the ProjectToolsCommandResolver to dotnet out of Cli.Utils because of the dependency on Microsoft.Build. Also added a EndToEnd test for tools ref using the MSBuildTestApp. 2016-10-04 18:59:44 -07:00
Livar Cunha
55c00a7e45 Adding a resolution chain to the command resolution chain that works based on a directory, more specifically, the publish directory. 2016-08-25 16:01:32 -07:00
Pranav K
1e753f7781 Replaces references to Microsoft.Extensions.PlatformAbstractions with Microsoft.Extensions.PlatformAbstractions.Internal 2016-04-29 16:06:23 -07:00
Bryan Thornbury
9f58651b6c PR Feedback and nearly full test coverage for resolvers
fix

resolve rebase issues
2016-03-07 14:45:16 -08:00
Bryan Thornbury
b813e2b849 Fixes #1649
make things work again

fix

Tests Passing

cleanup

fix

fix
2016-03-07 14:35:41 -08:00
Bryan
42cc39252e Refactor CommandResolver into individual CommandResolver Implementation
classes.

Write Unit Tests covering Composite DefaultCommandResolver and
ScriptCommandResolver.

baseline

Baseline2
2016-03-07 14:34:23 -08:00
Eric Erhardt
6468b14e1d Move to CoreFX build rc2-23901
Update .exe's project.json Target Framework from dnxcore50 to netstandardapp1.5.
Update .dll's project.json Target Framework from dnxcore50 to netstandard1.3.

Adding workaround for DataContractSerialization to src\dotnet\project.json to fix crossgen issue.
Build 23901 has a dependency issue that doesn't allow the runtime.any.System.Private.DataContractSerialization
package to be restored. When we move to a new build of CoreFX we should take this workaround out.
2016-03-03 16:41:55 -06:00
Livar Cunha
ebab175d17 Added a command factory where you can fix the output parameters that will flow to the commands, like configuration, outputpath and in the future, framework, runtime and base path. 2016-03-01 22:28:46 -08:00
Bryan Thornbury
c749bae962 Pipe configuration through CommandResolver
script changes to pipe configuration to test.ps1

debug commit, remove this commit

Change dotnet-test to invoke dotnet-test-xunit directly

build tests with configuration, framework, runtime in windows

Update testtargets in new build scripts

make configuration first arg to dotnet test

PR Feedback

update command factory

fix interface

test update
2016-02-18 09:57:30 -08:00
Bryan Thornbury
c1e28ae921 Refactor ScriptExecutor, add test cases for scriptexecutor.
Add TargetFramework and FullTargetFramework to compile and publish script
variables.

Add ProjectLocal Command Resolution Strategy.

Fixup ArgumentEscaper to not always quote things.

Fixes #1216
Fixes #1016
Fixes #982
2016-02-12 11:04:30 -08:00
Pranav K
33f1b8551e Compile Microsoft.DotNet.Cli.Utils in net451 2016-02-11 15:46:43 -08:00
Pavel Krymets
0f82ae37f3 Refactor output directory code 2016-02-09 08:52:59 -08:00
Livar Cunha
9c87983fdf When doing the argument escaping work, we changed the way we pass the depsfile to the host, this broke the dotnet test command. Moving the parameter back to its original and expected format. 2016-01-28 18:12:28 -08:00
David Fowler
6edac85dce Fixed copying output assets to the publish directory 2016-01-27 20:35:43 -08:00
David Fowler
a35ae177ff - Make all of the code looking for built assets use the OutputPathCalculator
- Project dependencies are always built into their specific folders and the main project is the only one that uses the output path and intermediate output path variable.
- Publish respects the output path for publish only, not compile as part of publish. This means that publishing multiple runtimes will stomp on each other. So don't do that. We can throw if you specify and output location and you haven't specified a specific combination of RID and framework. Alternatively it should probably just pick the first TFM/RID pair from the lock file. This is similar to how `dotnet run` works.
- Cleaned up the incremental build output formatting
- Use a single stream (output stream) since interleaving them was causing formatting issues (like losing random characters in the middle of outputting things).
- Didn't change how pack works, it still preserves the output structure when passing `--output`, this one is worth discussing. We could leave the build output inplace and only move the package to the output location. That's more consistent with how everything else works and can be a follow up PR.
2016-01-27 11:13:45 -08:00
Bryan
4c41c9699c Last necessary test changes
Fix the refactoring bugs

fix restore

downgrade version of package command test

Linux Test Script Fixes

use corehost instead of corerun for arg testing

don't copy corehost

fix scripts

Account for change in publish path, use corerun. Issue with AppContext.BaseDirectory in corehost.

Case Sensitive Reflector

wait for process exit

Fix bug in runtests.ps1

fix release build output path

fixup bug in runtests.sh
2016-01-23 14:32:50 -08:00
Bryan
cd9e5e2f08 Make the move off of * dependencies
move tests back to 23704

name changed, feedback
2016-01-23 13:01:37 -08:00
Bryan Thornbury
d1d23944df Changes to fix publish tests 2016-01-23 13:01:34 -08:00
Bryan
e794ad6a10 Basic Argument Forwarding and Escaping Code Additions/Changes 2016-01-23 13:01:30 -08:00
PiotrP
8274f5285b Enable resolving command paths from AppBase 2016-01-12 13:16:52 -08:00
schellap
907cf00654 Split corehost into serviceable DLL and EXE 2016-01-11 18:06:18 -08:00
PiotrP
9eed889217 PR Feedback 2016-01-11 13:10:55 -08:00
PiotrP
ec5a50dfe8 fix parameter name in CommandResolver.cs 2016-01-11 12:06:35 -08:00
piotrp
c5ce2eb753 Fixes issue #781 makes CommandResolver comply with new implementation of --depsFile 2016-01-11 02:36:21 -08:00
piotrp
5cd64066c4 Packaged Commands 2016-01-09 16:50:31 -08:00