3.1 release

site/jekyll/_posts/2017-07-02-3.1.0-release.md

@@ -0,0 +1,21 @@
+---
+title: "ReactJS.NET 3.1"
+layout: post
+author: Daniel Lo Nigro
+---
+
+I'm happy to announce the release of ReactJS.NET 3.1! This is a minor release with a few changes:
+
+ - [#388](https://github.com/reactjs/React.NET/issues/388) - ASP.NET Core middleware is now in a separate NuGet package. If you want to use the middleware to transpile JavaScript without pulling in the full ASP.NET MVC Core framework, you can just use the `React.AspNet.Middleware` NuGet package.
+ - [#421](https://github.com/reactjs/React.NET/pull/421) - Upgraded to JSPool 3.0. This has a few small API changes, but should not affect most sites unless you're messing with the internals of ReactJS.NET.
+ - [#421](https://github.com/reactjs/React.NET/pull/421) - The MSBuild task now has an assembly binding for `JavaScriptEngineSwitcher.Core`, which should prevent strange errors when the version of `JavaScriptEngineSwitcher.V8` does not match the version of `JavaScriptEngineSwitcher.Core`.
+ - [#413](https://github.com/reactjs/React.NET/pull/413) - The `DefaultEngineName` setting in JavaScriptEngineSwitcher is now respected, and can be used to force a particular engine to be used.
+ - [#416](https://github.com/reactjs/React.NET/pull/416) - `MaxUsagesPerEngine` is now available as a configuration option. *Thanks to [Halstatt](https://github.com/Halstatt)*.
+ - [#419](https://github.com/reactjs/React.NET/pull/419) - Server-side console calls (eg. `console.log`) now include the stack trace. *Thanks to [Halstatt](https://github.com/Halstatt)*.
+
+The ReactJS.NET project has also been upgraded to use the Visual Studio 2017 tooling ([#406](https://github.com/reactjs/React.NET/pull/406)). This means that if you want to modify ReactJS.NET itself, you need to be using Visual Studio 2017.
+
+Have fun, and as always, please feel free to send feedback or bug reports
+[on GitHub](https://github.com/reactjs/React.NET).
+
+— Daniel