11 Коммитов

Автор	SHA1	Сообщение	Дата
Doug Bunting	f830808d8f	Create a .NET Standard 1.1 version of System.Net.Http.Formatting.dll ... - bring System.Net.Http in from .NET Standard Library - use .NET Standard version of Newtonsoft.Json - bring other dependencies in transitively - create initial test project, mostly a duplicate of existing "NetCore" one nits: - write detailed information to msbuild.log - clean up trailing whitespace in a couple of test classes	2016-12-12 17:36:00 -08:00
Doug Bunting	ddf07644e0	Build s/ latest MSBuild / Visual Studio installed ... - #12 - find `MSBuild.exe` and `Microsoft.Build.Tasks.*.dll` for v14.0 before v12.0 - avoid code analysis warnings (about `static`) the latest compiler detects - correct suppression check ids - suppress MW1201 FxCop rule for `UriExtensions.TryReadQueryAs()` to avoid #16 nits: - add solution for tools - ignore .vs directory	2016-08-10 12:29:04 -07:00
dougbu	fd2f238846	Remove build.cmd fallback to v4 version of MSBuild.exe ... - we don't support .NET 4.0 and shouldn't build or test using the older target framework - testing is particularly problematic since some unit tests fail due to .NET 4.0 quirks (legacy System.Uri behavior in particular) - part 1 of fixes for #1960	2014-05-23 11:20:41 -07:00
dougbu	1e55e5173c	Add comment for %MSBuild% setting ... - CR follow-up	2013-11-12 20:54:27 -08:00
davidmatson	1a9445aa27	Run VS2013-compatible FxCop rules on VS2013.	2013-11-08 16:12:25 -08:00
dougbu	1bfee49f63	Get build working in any command window ... - Prefer VS 2013 (v12.0) version of MSBuild.exe and fallback to v4.0 when necessary - Do not rely on %Path% since that limits us to VS developer cmd windows - Match Microsoft.Build.Tasks*.dll version to MSBuild.exe, not type of cmd window - Have tested building in VS 2013, VS 2013 dev cmd window, and bare cmd window Requires either a FxCopCmd.exe.config binding redirect or David's "VS2013 FxCop compatibility" change for full VS 2013 support.	2013-11-08 16:06:26 -08:00
davidmatson	0f37426c4a	Create separate CodeAnalysis configuration. ... Remove SuppressMessage attributes from Release configuration. Also, cleanup project file settings/make consistent.	2012-11-08 14:20:29 -08:00
davidmatson	45c1223c1d	Report build failure, not success, when MSBuild returns a negative exit code.	2012-10-11 14:59:26 -07:00
anurse	c7c349dda0	Added explicit Platform=Any CPU option to build.cmd to ease builds in x64 environments	2012-06-01 10:52:21 -07:00
bradwilson	1c4d4c9351	Setting /nr:false for build.cmd, will stop MSBUILD.exe from sticking around after builds are finished.	2012-04-04 14:39:59 -07:00
bradwilson	0f8c45fe03	Initial revision.	2012-03-11 10:17:56 -07:00