6 ms·
Hot reload for ASP.NET works fine nowadays in VS and even with older versions of .NET. Dependency handling is still a large problem with .NET. Especially since
by AtNightWeCode 4y ago
Hot reload for ASP.NET works fine nowadays in VS and even with older versions of .NET.
Dependency handling is still a large problem with .NET. Especially since current is often used instead of LTS. There is also no good way of sharing code between applications.
Arrow functions, btw, solves the this/that problem in JS making React development easier etc.
- nso 4y agoWhat do you mean when you say there is no good way to share code between applications?
- AtNightWeCode 4y agoWhat I see a lot is private Nuget packages with common functionality used within several applications at companies. These are often binaries (one can place code in a Nuget packages but it won’t update, at least not last time I tested it). In the world pre GIT it was common to link in these files and build them along with the solution. Meaning, one did not have to try to align every .NET version or keep adding build targets to the Nuget packages.
- kcartlidge 4y agoThat's what I'm used to too. Shared code in Nuget packages in an internal Nuget feed. But definitely not binaries, as I've never had issues with Nuget packages not updating. YMMV - maybe you've been especially unlucky.