I'm happy to announce the release of ReactJS.NET 1.2! This is a minor release and includes a number of changes and fixes since version 1.1.3:

• Basic source map support. Source maps will now be available when accessing .jsx files directly. It's not supported for combined/minified files at the moment since none of the common .NET minifiers support source maps. (#8)
• React version upgraded from 0.12.0 to 0.12.1.

Server-side rendering:

• The HTML tag used as the component's container can now be changed. Previously it was hardcoded to be a div. (#45)
• The ID of the container element can now be changed. Previously it was always an auto-generated ID in the format "react1", "react2", etc. (#50)
• New Html.ReactWithInit helper method to render both the HTML component and its client-side JavaScript initialisation script. This is useful when rendering self-contained partial views containing React components. Thanks to BartAdv. (#42)

Under the hood:

• Allow custom JsonSerializerSettings to be provided. *Thanks to BartAdv. (#43)
• Switch various methods from private to protected virtual so they can be overridden. (#39)
• Use newer React factory syntax for instantiating components. (#46)

Have fun, and as always, please feel free to send feedback or bug reports on GitHub.

— Daniel

I'm happy to announce the release of ReactJS.NET 1.1.3!

In this release, the React version has been upgraded from 0.11.1 to 0.12. The main changes in this React release are that /** @jsx React.DOM */ is no longer required at the top of your JSX files, and React.renderComponent is now React.render. A few other API methods have changed as well. See the official announcement for more information on all the changes in this version of React.

ReactJS.NET 1.1.3 also adds preliminary support for using Google's V8 JavaScript engine on Windows, via Microsoft's ClearScript project. Previously ReactJS.NET only supported V8 on Mac OS X and Linux. This should be considered beta quality, in that it works but has not been stress tested in a production environment yet (whereas the Linux implementation has been). Future releases will make the handling of JavaScript engines more efficient.

Have fun, and as always, please feel free to send feedback or bug reports on GitHub.

— Daniel

I'm happy to announce the release of ReactJS.NET 1.1.2! This is a minor release and includes a number of changes and fixes since version 1.1.1:

• Error messages now contain more details, including file name, component name, line number and column number. This should make debugging a bit easier, especially if you're debugging without Visual Studio attached. (#17)
• JSX Namespacing is now supported (#37)

Have fun, and as always, please feel free to send feedback or bug reports on GitHub.

— Daniel

I'm happy to announce the release of ReactJS.NET 1.1! This is a minor release and includes a number of changes and fixes since version 1.1:

• React version upgraded from 0.10.0 to 0.11.1.
• Fixed an access violation exception when running in Release mode. Thanks to Paul Irwin for reporting and jlchmura for fixing.
• Always transform JSX in bundles, even when the very first file doesn't have the /** @jsx React.DOM */ directive. Thanks to Rick Beerendonk.
• ES6 transforms are now turned off by default since they can conflict with other ES6 transpilers like Traceur. Check the documentation to see how to enable them. Thanks to Aleksander Heintz.

Have fun, and as always, please feel free to send feedback or bug reports on GitHub.

— Daniel

I'm happy to announce the release of ReactJS.NET 1.0! There have not been many changes since version 0.2, but I've decided to release this version as 1.0 since the API is becoming fairly stable, I'm now using it in production for one of the pages on my personal site, and most importantly, I've met the end goal I set when starting the project — Getting it to run on Linux :)

Changes since 0.2:

• Full Linux and Mac OS X (Mono) support via Google's V8 JavaScript engine, the same engine used by Google Chrome and Node.js. Windows support for V8 is a lower priority but will come soon.
• ES6 transforms (via jstransform) enabled out of the box, meaning you can use some ES6 features such as arrow functions, short object notation and classes in your JSX files.

Have fun, and as always, please feel free to send feedback or bug reports on GitHub.

— Daniel