| Age | Commit message (Collapse) | Author |
|---|
|
* Display contents of init-tools.log.
* Display log on failure in init-tools.log.
* Revert "Display contents of init-tools.log."
This reverts commit d81a4b61c8356d5254192b20a92e473352892b62.
* `init-tools.sh` displays detailed log on error.
* Consistent goto `:error` flow in `init-tools.cmd`
|
|
The azureedge hostname will have us hit the CDN which should provide
better performance for folks that are not close to the US datacenter
we have our blobs in.
|
|
This file is used in init-tools.cmd/sh, and replaces the "generated"
project file used previously. Because we are using MSBuild projects for
nuget restore now, we are able to "parameterize" the version of
Microsoft.DotNet.BuildTools based on an MSBuild property which is passed
in to the "dotnet restore" command in init-tools.
|
|
|
|
Moves the copy of Tools-Override to run.cmd/sh and always do it so that
we don't keep getting into incremental tools issues when we make changes
in Tools-Override directory without a BuildTools version update which forces
an update of Tools.
|
|
|
|
|
|
things (#14062)
* Used GenerateBuilds.ps1 script to generate the P2P references from the project.json files in ref
* Update refs to build with ProjectReference's instead of package references
This deletes all the ref\project.json files and instead adds ProjectReference
to other refs that are used to build.
There is only one exception which was System.Net.Http which needed a project.json
to get the net46 targeting pack otherwise everything else is P2P.
* Update Reflection.Emit contracts to support latest version of contracts
* Add depproj to get windows.winmd support when building refs
* Special handle System.Net.Http ref project to deal with net46 targeting pack
* Moved CLSCompliant to SecureString ctor instead of type
* Add P2P reference from S.IO -> S.R.Extensions
* Add additional ProjectReferences to more ref projects after master rebase
* Start binplacing ref assemblies and disable rest of build
* Simplify all ref projects to only build for netcoreapp (default target group)
* Only binplace netcoreapp refs
* Allow Reference's to be resolved from targeting pack directories
* Use GenerateBuilds.ps1 to convert src project.json refs to References
* Allow overriding stuff in Tools
* System.Runtime src project building against targeting pack
* Re-purpose GenerateBuilds.ps1 to re-write src references
* Only build csproj files in src.builds
* More custom stuff in GenerateBuilds.ps1
* Binplace all netstandard assemblies into netcoreapp as well.
* Add project.json to System.Collections.Immutable
* More custom generatebuilds.ps1 stuff
* Normalize csproj files before running GenerateBuilds.ps1
* Better match the replaced 'None Include="project.json"' line.
* Another missing project.json inclusion in csproj
* Remove ExcludeFromCodeCoverageAttribute from Immutable project
* Include another project.json
* Add some P2P references
* Add another project.json include
* Disable Http.Rtc project.
* Disable two more UWP projects and another P2P ref"
* More Cleanup
* Run GenerateBuilds.ps1 to re-write all nuget refs as <Reference>'s
* Binplace netstandard runtime assemblies to netcoreapp as well.
* Re-hook all src projects into build.proj
* Fix bin clashing caused by bad ProjectReference metadata
* Use 'copy' instead of 'cp' in init-tools.cmd. Add copying to init-tools.sh as well.
* Correct casing of windows.winmd in depproj
* Disable System.Memory.csproj outside of Windows
* Fix unix exclusion of System.Memory, and include vbproj files
* Fix VisualBasic compilation
* There was an extra definition of MemberTypes that was internal to the
assembly. It's now defined in System.Private.CoreLib, so I deleted the
extra here.
* There was an invalid call in Operators.vb that I fixed.
* Add additional project references and configuration fixes after rebase
* Fix build warnings in ref projects
* Fix build warnings in src projects
|
|
(#12475)
|
|
We need the latest compatibility mappings for NuGet but the CLI hasn't
yet picked up a new NuGet drop.
Workaround this by manually patching the NuGet.Frameworks.dll in CLI.
|
|
* Upgrade CLI, buildtools for RTM shared framework.
* Upgrade buildtools, add new platforms to init-tools (ubuntu 16.10, fedora 24, opensuse 42.1).
|
|
|
|
output (#11059)
* Enable option to suppress non-error output from the console output for
init-tools.
* Redirect standard output to log
* Remove unneccesary arg
* Add Linux init-tools changes
* revert dotnet to x64
* Remove echo line from run.sh
|
|
This lets us publish a package and consume it immediately from our
builds.
Without this our CI clients were relying on an HTTP cache of our myget
feeds and failing when we updated projects or buildtools.
|
|
Downloading from Azure can transiently fail for a number of reasons. Add
some retry logic when downloading to avoid transient failures. For *nix
variants add a retry value when using curl (wget retries by default).
|
|
Clean up all non-essential references to DNXCore50.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Echo is unconditionally turned off in batch files making it hard to debug
issues. This change provides a way to leave echo on by setting the _echo
environment var to on.
|
|
Correctly cleaning up the ToolRuntime folder once a new version is required.
|
|
|
|
Include capitalization fixes for NETNative packages to avoid xplat nuget race condition.
|
|
- We have moved our feeds to our enterprise myget
account (dotnet.myget.org). Start pulling from there and use the v3
feeds since we are restoring with tools that understand them.
- Remove some no longer needed NuGet commands and sources
|
|
|
|
Adds Clean.cmd and Sync.cmd
There is also an option added for disabling batch restore of packages
during the build. Right now it restore is still enabled by default
but eventually it will be disabled and restore will only happen when
you call sync.cmd or build an individual project.
To disable batch restoring during build people can do one of 2 things:
1) set RestoreDuringBuild=false in your enviroment
2) pass /p:RestoreDuringBuild=false to build.cmd
|
|
There were two issues that we were hitting (with the first masking the
second).
1. We seem to hit https://github.com/dotnet/coreclr/issues/2153 most of
the time we tried to restore the tool-runtime (which manifested itself
as a AV in CSC). Until that issue is fixed, we can use the
COMPlus_ReadToRun environment variable to work around the issue.
2. We changed the unzipping part of the powershell init script to use
System.IO.Compression.FileSystem, but that did not work on Windows
7 (Add-Type refuses to load the assembly within PowerShell). I added
some extra logic to fall back to the shell stuff when we can't load the
managed libraries. This does mean we'll pop UI when restoring the tools
on Windows 7, but there's no real harm in doing so.
Fixes #5493
|
|
While we would like to use 'Latest' as the version for dogfooding
purposes, we have to keep our builds unblocked and there is currently
a breaking change we have to react to. So to unblock we are fixing
to a particular version we know works.
|
|
Move init-tools to the top of build.cmd
Clean-up init-tools.cmd script and put most stuff out into a log file
Update build.cmd to add timestamp during logging also add timestamps
around the batch restore target so we can see how log it takes.
Adds the Summary option which will dump all the warnings and errors
at the end of the console output so the are more noticable.
Also cleans out the unnecessary restoring of packages.config files as we
no longer have any of those.
|
|
which causes some invalid arg error.
[tfs-changeset: 1564938]
|
|
are easier to recover from.
[tfs-changeset: 1563091]
|
|
[tfs-changeset: 1562939]
|
