nx-electron VS nx-dotnet

I'm honestly not overly familiar with the "typical" setup of an Electron app (if there is such a thing — the docs make it sound pretty open-ended). I've only ever used it in the context of nx-electron (not that I can recommend it — it's not up-to-date with the latest versions of nx/Angular and it's kind of harrowing to get working even in the best case). But not being able to import anything in your entry-point seems like an unusual constraint — how are you bootstrapping the application?

I worked full stack with .net and angular for a year. I would say that is you think too OOP, you might try to do things that typescript doesn't do well. Like extending one class with multiple base clases. I've been working with Nestjs for one year or so in a personal project and I think it's amazing. You can do simple things like MVC and rest apis with little efforts. You can also work with more complex patterns like DDD and event sourcing pretty much out of the box. Because it is also JavaScript and node you can use a plethora of packages that solve your problems similarly as .net like Automapper, typeorm/mikroorm (entity framework like). In addition to a ton of open source projects that are using nestjs. Check https://github.com/nestjs/awesome-nestjs so you can explore how to get started. I would recommend you to use NX.dev to work your mono repo, it is super powerful and easy to maintain a full node mono repo. And it even has a plug in to add c# .net core projects as well https://github.com/nx-dotnet/nx-dotnet. So you can still leverage on the same tech you already know for more complex things like Identity server.

This is why DX is so important if you're going to go down the monorepo path. Angular has stuff like Nx (https://nx.dev/using-nx/caching) which helps a ton. I'm not really familiar with any .NET focused monorepo tooling. It looks like there is a .NET plugin for Nx (https://github.com/nx-dotnet/nx-dotnet) but I haven't used it so no clue how well it works..