search

dsuryd / dotNetify-react-template

Real-time React SPA template using dotNetify.
https://dotnetify.net/react
Apache License 2.0
203 stars 57 forks source link

.Net version of Dotnetify #8

Closed ibuildit closed 6 years ago

ibuildit commented 6 years ago

Hi,

I have created a .Net based version of this to be used inside Microsoft Service Fabric (that only works with .Net). It still uses all the .net core stuff, I just shuffled around the dependencies so it uses nuget to pull the dotnetcore libs, while still being compliant with service fabric using .net as the base.

Do you want it? You could probably figure out the best way to support both, if at all. Perhaps a project that contains only a help file on the steps of converting from .net core to .net base?

dsuryd commented 6 years ago

That's cool! I can either add a link on the readme page to your fork, or you put it in a new folder 'ServiceFabricTemplate' or 'ServiceFabricDemo' and PR me.

ibuildit commented 6 years ago

Hi again!

I've been busy but I'm trying to complete this for my own project. Service Fabric now supports .NET Core, so this is now running on .Net core stateless service.

I have a problem though. I get this error message, and I can't figure out why.

I know it's related to that there is no state, and it's related to react not getting any state from backend.

screenshot_28

See here (from firefox react debug), that one has a vm object (the normal version), the other one does not (SF version). As you can see everything except state works. The login works, the UI element works...etc.

I don't know how to debug this, maybe you could help me figure it out?

screenshot_29 screenshot_30

It runs inside the SF cluster, but is reachable at an endpoint

screenshot_31 screenshot_32

That directory looks like this (in dev. mode a node is a directory on your local machine). The project is called "PNL", so that's why that is there.

screenshot_33

I'm new to React, so any ideas would be appreciated. Thank you!

dsuryd commented 6 years ago

SignalR requires persistent connection to the same SF node, did you already configure it?

To see dotNetify messages in the console tab, add dotnetify.debug = true in the app.js. If you don't see data coming in in response to initial vm request, check the network tab for errors (if using websocket, look at the data frames.)

dsuryd commented 6 years ago

Closing this due to lack of activity. Feel free to reopen if there's progress.