Of some components we cache the HTML output on the server. However, the current container id generation is based on identity. This results in duplicate ids in the HTML, causing components to be instantiated in the wrong divs. We solved this by using a non-deterministic algorithm:
Good catch, thanks!
Use GUIDs for container IDs, rather than sequential IDs. Closes #230
Any ETA of when the next version will be released to Nuget with this fix? We just ran into when enabled caching on our site.
Sorry, didn't see your comment. I've got a few updates, so I'll push a new build tonight.
ReactJS.NET 2.3 (including this fix) was pushed on 11th April