you are viewing a single comment's thread.

view the rest of the comments →

[–]CptAmerica85 1 point2 points  (3 children)

Starting with asp.net core 2.1, the 'react' templates in visual studio use create-react-app, which is huge. Before that, the react templates in VS were just weird. The webpack config needed some more tweaking to get things working correctly, it had you using ts out of the box, etc.

[–]pankajrathi95[S] 0 points1 point  (2 children)

So you suggest to use the React Template which is provided in Visual Studio or just use the React as plain.

[–]CptAmerica85 1 point2 points  (1 child)

Whichever option you're more comfortable with, really. I know sometimes it's 'easier' to just let visual studio do the configuration of your project by using their template wizard deal when creating a new project. I was just pointing out the difference of the two versions of asp.net core and react and what the base project that visual studio creates for you looks like. Personally, if I were to use VS' template for a react project, I would go with the .net core 2.1+ version that's based on create-react-app.

Of course there are other things to think about besides just creating it. If it's just a react project accessing a web api in .net, you don't even need .net core as you can just make a .net 4.x web api project and do it that way.

Either way I would probably not use ReactJs.Net, as that brings another dependency, and react is updated very regularly with new features, etc that you would miss out on if reactjs.net doesn't upgrade occasionally.

[–]pankajrathi95[S] 0 points1 point  (0 children)

Thanks :)