Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/mono/corefx.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2017-05-17Increment versions post 2.0Eric St. John
2017-04-10Updates how we define which key an assembly usesWes Haggard
Now instead of Use*Key a project can instead define the assembly key in the project (genreally the common dir.pops for a project) using the AssemblyKey property. The accepted values are Open, ECMA, MSFT, Test. This change allows for a repo to set the default key they want to use for projects. In corefx we have switched the default to use the Open key instead of the old BuildTools default of MSFT key. As part of this update we are explicitly setting the AssemblyKey in all the library projects (although it is really only necessary for projects that aren't the default). Also with this change we are updating all the new libraries that have not yet shipped stable (compared to our 1.1 release) and making them use the Open key. Which means that for prerelease dependencies there might be some binary breaking changes to consume. The following libraries ahven't shipped so there key is being changed from MSFT to Open: Microsoft.XmlSerializer.Generator System.CodeDom System.Configuration.ConfigurationManager System.Data.Odbc System.DirectoryServices System.DirectoryServices.AccountManagement System.DirectoryServices.Protocols System.IO.Ports System.Json System.Memory System.Net.HttpListener System.Net.Mail System.Net.ServicePoint System.Net.WebClient System.Net.WebProxy System.Private.Xml System.Private.Xml.Linq System.Security.Cryptography.Xml System.Security.Permissions System.Transactions.Local System.Web.HttpUtility
2017-03-17Change assembly version in csproj instead of dir.props (#17238)Santiago Fernandez Madero
2017-03-17Fix System.ComponentModel.TypeConverter failing tests (#17206)Santiago Fernandez Madero
* System.ComponentModel.TypeConverter failing tests
2017-02-08Prepare uap package (#15866)Jose Perez Rodriguez
Prepare uap package
2016-12-08Binplace NETCoreApp package contentsEric St. John
Set up a separate destination for package contents for NETCoreApp since it won't necessarily be everything that we build. Libraries were determined as follows: 1. If its currently in NETStandard.Library its in. 2. If it was a ref in NETCoreApp before its in. 3. If its part of the reference closure for 1 or 2 its in. 4. If it was a lib only in NETCoreApp its in, but only lib. 5. If its part of the lib closure for 1-4 its in, but only lib.
2016-10-05Update project ToolsVersions to 14.0 (#12355)Alex Perovich
2016-09-15Port System.Timers.Timer to dev/api.Lakshmi Priya Sekar
2016-08-24Central nupkg versioning & library assm versioningEric St. John
This moves to a central versioning scheme for all packages that is tied to the product release. 1.1 will include packages all with a common version.