Commit Graph

13 Commits

Author SHA1 Message Date
Nate McMaster d452ff44b3
Include portable symbols in nupkgs (#2009) 2018-02-02 11:14:25 -08:00
Nate McMaster 34054339ed Upgrade to build tools 2.1.0-preview1-15651 2017-12-28 14:10:04 -08:00
Pranav K b2e2719e43 Make AspNetCoreSettings actually work 2017-12-28 09:40:21 -08:00
Nate McMaster 5acef44685 Use MSBuild to set NuGet feeds instead of NuGet.config 2017-11-20 12:30:45 -08:00
Nate McMaster 4d737af167 Pin tool and package versions to make builds more repeatable
Part of aspnet/Universe#575
2017-11-01 18:12:08 -07:00
Ryan Brandenburg c28940c915 Add RepositoryRoot 2017-10-18 09:37:36 -07:00
N. Taylor Mullen 059264ba34 Fix RazorAddin project.
- Move assembly attributes to work with incremental compilation.
- Utilize Mono.Addins from nuget.org.
2017-09-29 17:46:51 -07:00
N. Taylor Mullen 3c73812f8a Revert "Revert "Add Microsoft.MonoDevelop.RazorAddin.""
This reverts commit fa0990fe00.
2017-09-29 17:17:44 -07:00
N. Taylor Mullen fa0990fe00 Revert "Add Microsoft.MonoDevelop.RazorAddin."
This reverts commit fca4f23895.
2017-09-29 17:08:17 -07:00
N. Taylor Mullen fca4f23895 Add Microsoft.MonoDevelop.RazorAddin.
- As part of this work I also added `Microsoft.VisualStudio.Mac.LanguageServices.Razor` to be the Visual Studio for Mac specific Razor code.
- Added MSBuild infrastructure to automate creation of MonoDevelop addins (MPacks). This work enables us to not have a dependency on a specific version of monodevelop and does not require us to have tool-prerequisites on the box. Every build outputs the mpacks into the artifacts/build directory.
- Built in build-level metadata pieces to workaround how addins are typically developed. They are usually authored C# first and then config files are generated after the fact; with this changeset we auto-generate the addin.info and its corresponding assembly attributes. Both of these take information directly from the build system.

#1696
2017-09-29 16:26:50 -07:00
Ryan Nowak f3fecabe04 Bump Roslyn to a 2.6.0 build
Fixes #1654
2017-08-30 15:30:57 -07:00
Nate McMaster 471722eba1 Use PackageLineup to manage PackageReference versions
This uses a feature of KoreBuild which will select PackageReference
versions based on a lineup file. This helps unify versions between repos
and helps us ensure we are consistent across multiple components.
2017-08-25 15:44:05 -07:00
Nate McMaster 4cadee2762 Use Directory.Build.props/targets (#1641) 2017-08-23 12:24:57 -07:00