Listor- Showcasing React and .NET Core
For both React and for .NET Core (specifically ASP.NET Core and Entity Framework Core), I got sick of playing around with little prototypes and decided to build an application. Listor is my first proper application I have built using both these technologies. It is a simple list-maker application- nothing fancy. But I have been using it since I put it up and it has come in handy quite a bit.
I am quite impressed with .NET Core (or I should say “the new .NET” - to mean not just the .NET Core runtime, but .NET Standard, the new project system, ASP.NET Core, EF Core, and let’s say even the latest language improvements to C#). So much so, that it is going to suck a bit going back to writing traditional .NET Framework stuff for my day job.
My journey with React was much more convoluted. I started with it, took some time getting into the whole idea of JSX, but eventually was quite impressed by it. Then I got into the rabbit hole of setting up the environment, boilerplates, and then Flux and then Redux - and then I got jaded real fast. I had to then reset myself back into vanilla React to see if I could just get stuff done with it. As far as this little application is concerned, it did the job nicely. I used create-react-app to set it up.
EF Core worked out nicely for this application - I am not doing anything crazy anyway, so those basic use cases are already nicely covered. In terms of the build process, rather than treat the build output of the client application as content and simply use something like
app.UseFileServer(), I opted to go with compiling them as embedded resources, and built an
AssetServer middleware that would cache it in-memory and serve it out fast. Again, I didn’t have to, but it turned out okay.
All in all, the application turned out to be useful, and I think it will serve as a nice playground for when I need to try out new technologies as they come out.