-
Notifications
You must be signed in to change notification settings - Fork 927
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ETA for .NET Core Standard Dependency? #294
Comments
@RichardD012 is working on porting the dependencies as well as ReactJS.NET itself to .NET Core 😄 |
@Daniel15 Any update on @RichardD012's effort to port it to .NET Core? |
I currently have a working version if you look at my fork. The required dependencies work in Windows using the Vroom Js renderer. Currently what is holding back a PR is that the dotnet solution hasn't been completely rebuilt to match the exiting legacy solution. However, they both work independently and the MVC6 Sample uses that. I'm actually using it in a side project with a custom Nuget config for the solution pointing to local versioned packages. This is also present in the example as it using the unnerved JSpool for dot net core. |
Thanks @RichardD012 !! I attempted to get your code working my dev machine. But I get these errors: Severity Code Description Project File Line Suppression State Ihave been unable to resolve these errors for 2 days now. Any idea why I am getting these? |
Which version of the ASP.Net Core are you running? If you |
@RichardD012, I get this when I run the version command 1.0.0-preview2-003121 |
Same here, would gladly have a solution which works with RC2. |
Now that JavaScriptEngineSwitcher officially supports ASP.NET Core, I'm going to release an official build of ReactJS.NET for ASP.NET Core. First step is an official release of JSPool for ASP.NET Core, which I've started working on. The JavaScriptEngineSwitcher release is just an alpha version, so this will probably be an alpha version too. |
Hey all! My team is looking to include this in our enterprise solution. Any progress on the netcoreapp1.0 framework? |
References #16 References reactjs/React.NET#294
First step is done, I just added a .NET Core build for JSPool here: Daniel15/JSPool@4e1ecb2. I just need to do more testing, and then update ReactJS.NET to use it too. Since JavaScriptEngineSwitcher 2.0 is currently an alpha release, this will also most likely be labelled as an alpha too. |
All tasks for ASP.NET Core support are being tracked in this milestone: https://github.com/reactjs/React.NET/milestone/4 |
This still needs testing to be done and the examples updated to be compiled for .NET Core, but it's a start. References #294
I just want to use React with my *"MVC 6"(edited) project.. |
I just released ReactJS.NET 3.0 RC1, which has support for .NET Core. Documentation and an updated tutorial will come before the final release. 😄 |
I like it.. will check it out asap.. |
I followed the tutorials and have looked at most of the comments, im trying to add this react.net to my MVC 6 project, it's the core 1 (.net) version, i changed the depedecies from netcoreapp to net452 , but I just get the error >> "The project does not specify any target frameworks in project.json" << |
Daniel15, worked right out of the box for me! Thanks so much for pushing this out! |
Stable release of ReactJS.NET 3.0 is out, with support for .NET Core: https://reactjs.net/2016/10/3.0.0-release.html |
@chikehenderson - Please try with ReactJS.NET 3.0 and let me know if you still encounter issues. You might find the tutorial useful: https://reactjs.net/getting-started/tutorial.html |
@Daniel15 - I almost gave up, I will check it out.. thanks |
Awesome. It worked out of the box with 3.0. Thanks |
I had to add VroomJs.AssemblyLoader.EnsureLoaded(); in my startup on windows to prevent this error. Using React.AspNet 3.0.0 in a Microsoft.NETCore.App 1.1.0. |
Good catch @chriscamplejohn! Would you like to send a pull request to add that to the documentation? |
Hello,
I wanted to verify that this is still an issue and a fix is in the works. There have been a couple of related issues that have been closed without a full resolution. #278 and #275.
In the related issues, it was mentioned that the Js rendering engine was the holdup. There are now a few options available, including VroomJs, which @pauldotknopf has ported to .NET Core.
Thanks,
Clayton
The text was updated successfully, but these errors were encountered: