Increase version to 2.8.2

Core/AssemblyVersion.cs

@@ -14,5 +14,5 @@
 // command to change the version number which, I guess, produces an incompatible 
 // assembly in the presence of strong names (strong naming prevents two assemblies 
 // from linking together without an exact match.)
-[assembly: AssemblyVersion("2.8.1.0")]
-[assembly: AssemblyFileVersion("2.8.1.0")]
+[assembly: AssemblyVersion("2.8.2.0")]
+[assembly: AssemblyFileVersion("2.8.2.0")]

Readme.md

@@ -33,22 +33,16 @@ If you just want the [core libraries](http://core.loyc.net/), you can find them
 How to build
 ------------
 
-Open Loyc.netfx.sln in Visual Studio (or Loyc.netstd.sln for the .NET Standard edition), set the build configuration to Debug.NET45, and build it!
+Open Loyc.netfx.sln in Visual Studio (or Loyc.netstd.sln for the .NET Standard edition), set the build configuration to Debug, and build it!
 
-If Visual Studio complains about OxyPlot, the easiest fix is to unload the LoycCore.Benchmarks project (nothing depends on it).
-To fix it properly, open Core\Loyc.netstd.sln, right-click the solution, choose "Restore NuGet packages", build the solution (just to make sure it worked), and then return to the original solution.
+If Visual Studio complains about OxyPlot, the easiest fix is to unload the LoycCore.Benchmarks project (nothing depends on it). To fix it properly, open Core\Loyc.netstd.sln, right-click the solution, choose "Restore NuGet packages", build the solution (just to make sure it worked), and then return to the original solution.
 
-What's the deal with the binaries?
-----------------------------------
-
-LeMP and LLLPG are self-hosting: they rely on themselves to help build themselves. Therefore, a binary copy of LeMP and LLLPG is kept in the `Lib\LeMP` subdirectory. However, to avoid bloating the git history, it is rarely updated. Consider checking [here](https://github.com/qwertie/ecsharp/releases) for a newer release. As of late 2016, releases still contain the .NET 4 Release build rather than .NET 4.5, because the Visual Studio syntax highlighters are still built with VS 2010 (and compatible with VS 2010, VS 2012, VS 2013 and VS 2015). As soon as someone asks me to switch the main release .NET 4.5, I will.
-
-Of course, you can also just build Loyc.sln to get a .NET 4.5 or even .NET 3.5 build. Compatibility with .NET 3.5 is aided by the Theraot compatibility library.
+If you need to change any .ecs or .les source files (Enhanced C# or [LES](http://loyc.net/les/)), you'll need to install the latest LeMP extension for Visual Studio, which can be found on the [Releases page](https://github.com/qwertie/ecsharp/releases). There is no _build step_ for these files, so the extension is not required for building. Unfortunately VS Code is not supported at this time - let me know if you need support.
 
 How to publish new versions
 ---------------------------
 
-This is not necessary for pull requests: qwertie will take care of versioning.
+This is more of a note-to-self than anything. Pull-requestors can ignore it.
 
 1. Rebuild all (Release configuration in Loyc.all.sln) and run tests (Tests.exe)
 2. Update version in Core/AssemblyVersion.cs

appveyor.yml

@@ -1,4 +1,4 @@
-version: 2.8.1.{build}
+version: 2.8.2.{build}
 
 # Try to fix "The project file ... is not supported by MSBuild and cannot be built."
 image: Visual Studio 2019
@@ -12,7 +12,7 @@ before_build:
 build_script:
     # First, set some environment variables.
     # SEMVER is set manually. Not sure how this can be automated.
-    - set SEMVER=28.1.0
+    - set SEMVER=28.2.0
     - echo %APPVEYOR_REPO_TAG%
     # Build packages as SEMVER-ci{build}
     - ps: if ($env:APPVEYOR_REPO_TAG -eq $True) { $env:PKG_VERSION = $env:SEMVER; } else { $env:PKG_VERSION = "$($env:SEMVER)-ci$($env:APPVEYOR_BUILD_NUMBER)"; }