Commit graph

27 commits

Author SHA1 Message Date
Livar Cunha
a9e12e0336 Updating core packages to rc3-24123-01 2016-05-23 17:19:11 -07:00
Sridhar Periyasamy
0c463c281f Remove '--infer-runtimes' option for 'dotnet restore' when restoring
TestAssets.
2016-05-23 17:04:32 -07:00
Sridhar Periyasamy
d2188cd95a Move the CLI corefx dependencies from RC2 to RC3 - rc3-24113-00.
- Disable crossgen for windows.Tracked by - https://github.com/dotnet/cli/issues/3059
- And also fix #2974
2016-05-23 17:04:29 -07:00
eerhardt
f8a155a4e6 Updating CoreFx to rc2-24027 2016-04-27 05:41:53 +00:00
Peter Marcu
02f232d4ab Revert "Revert "Updating CoreFX to rc2-24022"" 2016-04-22 16:39:44 -07:00
Peter Marcu
390946f531 Revert "Updating CoreFX to rc2-24022" 2016-04-22 16:01:51 -07:00
Andrew Stanton-Nurse
ef0ca39da1 Memory usage improvements in build (#2626)
* Use a WorkspaceContext in dotnet-build to cache project data across
multiple compilations in a single build action
* Dramatically reduce string and object duplication by introducing a
"Symbol Table" that shares instances of NuGetVersion, NuGetFramework,
VersionRange and string across multiple lock-file parses

Test Results:
* Testing was done by compiling Microsoft.AspNetCore.Mvc (and it's
dependencies) and taking memory snapshots after each compilation in
dotMemory
* We used to allocate ~3MB and deallocate ~2.5MB on EACH compilation in
a single build action. This has been reduced to ~120KB
allocated/deallocated
* After introducing WorkspaceContext, total memory usage spiked from 6MB
across the whole build action to about 13MB, introducing the symbol
table dropped it back to about 5-6MB.
2016-04-22 15:01:56 -07:00
Eric Erhardt
e420515c2b Updating CoreFX to rc2-24022 2016-04-22 10:58:43 -05:00
Bryan Thornbury
83d78129db t Convert Test Assets to Microsoft.NETCore.App
fix dotnet-compile-fsc failures

fix test failures
2016-04-19 11:08:27 -07:00
eerhardt
eb4952df27 Updating CoreFx to rc2-24018 2016-04-18 05:23:16 +00:00
eerhardt
070650ebac Updating CoreFx to rc2-24015 2016-04-15 05:25:53 +00:00
Matt Ellis
d0ac16129d Update package dependencies to rc2-24008 2016-04-08 04:05:26 -07:00
eerhardt
3afd85068a Updating dependencies from last known good builds 2016-03-31 11:57:21 -05:00
eerhardt
ea984c50c7 Updating dependencies from last known good builds 2016-03-30 11:49:37 -05:00
eerhardt
7eb9d07fb5 Updating dependencies from last known good builds 2016-03-29 15:59:19 +00:00
eerhardt
cefed77ca9 Updating dependencies from last known good builds 2016-03-28 17:27:54 +00:00
eerhardt
ed887d183a Updating dependencies from last known good builds 2016-03-25 16:48:25 -05:00
Eric Erhardt
1febe48d71 Updating CoreFX version to rc2-23924 2016-03-24 16:05:24 -05:00
Eric Erhardt
a5813791d5 Updating CoreFX version to rc2-23923 2016-03-24 16:04:37 -05:00
eerhardt
9bc478660a Updating dependencies from last known good builds 2016-03-24 16:02:33 -05:00
eerhardt
8953400eee Updating dependencies from last known good builds 2016-03-14 17:58:13 -05: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
Eric Erhardt
3da5ae70e2 Remove NuGet.Config files for test projects.
Fix #1316
2016-02-18 13:03:28 -06:00
Andrew Stanton-Nurse
236fcd8f95 update everyone to 23811
add a little hackiness to the build script to use 23811 in the stage 0 as well
2016-02-11 10:38:59 -08:00
Eric Erhardt
74d8051f79 Bump CoreFx to rc2-23810 2016-02-10 13:50:28 -06:00
Piotr Puszkiewicz
48797ea80a Bump CoreFx to rc2-23808
Workaround for issue 1294

Improve crossgen notifications
2016-02-09 15:49:45 -08:00
Eric Erhardt
3d14caceff Test directory refactoring step 1.
Moving TestProjects and TestPackages under root 'TestAssets' folder.

Partial fix #1250
2016-02-08 20:35:22 -06:00