8
15 Comments

Anyone using the .NET stack?

Interested to get to know people using the .NET stack to build their indie businesses, as I'm considering doing so as well.

  • How has your experience been so far building with .NET?
  • What NuGet packages have you been using?
  • What are you building?

Cheers,

on June 25, 2021
  1. 2

    I love dotnet core! C# is one of the best languages I've used wrt ergonomics and performance. .NET Core adds onto this by providing a whole ecosystem of mature, battle-tested libraries for common web / SaaS app requirements.

    Nuget packages I like:

    • EntityFramework - Seriously, don't need another ORM
    • XUnit - For testing
    • MediatR - For messaging (makes separation of concerns and CQRS easy!)
    • DBUp - For data migrations (yes, I like to do things explicitly over implicitly)

    Building:

    I'm building SaaS Boilerplate for .NET Core and NextJS (Frontend / Web Tier). Found myself building the same things over and over again - authentication, payment integration, email infra, software architecture, etc. Thought it would speed my iterations up and others might find it helpful as well. https://cloudseed.xyz/

  2. 2

    👋 I’m an experienced .NET architect. It is my preferred stack. I’m particularly excited about Blazor for the front-end.

    Aside from the core packages I recommend checking out FluentAssertions for testing. AutoFixture.AutoMoq is great too for eliminating a lot of setup code in tests.

    Following the playbook of starting with an info product I’m working on an ebook: https://StartBlazor.com

    My longer term project is to build something in finance related to fundamental security analysis.

    1. 2

      Blazor is great. For one of my client app we decided Blazor and application development time is super fast. React and others can't match to the speed of development. The only issue right now is the limited third party components.

      1. 1

        Did you build internal app or public? Is it Server or WASM? IS Server one connection stable for mobile connections?

        1. 1

          It's for a corporate client built using Blazor Server not WASM. Its a desktop site, not for mobile view.

  3. 2

    Yep, it's my go-to tech stack. It's a very robust platform and with the advent of .netcore, hosting is a lot cheaper than it used to be. Plus M$ are really pumping in the support for developers so a lot of the tools we used to have to pay for are now free -and really feature rich.

    • Love .Net and it's community so great -although years gone by it was a lonely existence outside corporates
    • Masses depending on what the requirement is from IoC, ORM, templating, sending SMS, broadcasting messages etc
    • Sales order aggregation platform but we use it for e-commerce and loads of other stuff
  4. 1

    I'm using Xamarin for the frontend of an app, and building it in C#. For the backend I'm using Elixir though.

  5. 1

    I'm currently working on a project with a .NET backend, I'm using ASP.NET Boilerplate using an angular front-end, eventually, when my first iteration of this project is done, I'll most likely upgrade to ASP.NET Zero but don't want to make that investment just yet.

    https://aspnetboilerplate.com/
    https://aspnetzero.com/

  6. 1

    I use dot net and love it. I know c# really well and that makes me very productive which is the important factor for me. I use react with typescript on the frontend and that combo works for me.

    As far as nuget packages I use Dapper, fluent assertions, Xunit, and Voyager (my own package) to name a few.

  7. 1

    I’ve used C# for MVC and now using Blazor server for the website and will be using Blazor web assembly for iOS/Android + website account sections.

    Mainly just using MySQL/Newtonsoft Json & Amazon S3 packages.

    Building a service platform and app (b2b and c2b).

  8. 1

    I use .Net Core, SQL Server and Angular. I use a variety of nugets but mainly asp.net core identity and efcore

  9. 1

    .Net Core backend, React front end has been my go-to for a while now. It’s great! C# is quite nice to work with. As for Nuget Packages I highly recommend Ardalis.ApiEndpoints. Also, I recommend checking out Microsoft’s sample repo, https://github.com/dotnet-architecture/eShopOnWeb It contains a lot of good ideas in terms of .Net architecture.

    I’ve been working on cofisoftware.com for a few years now and we’ve enjoyed the .Net/React stack.

  10. 1

    I am using .NET (C#) in most of my backend solutions. For my daytime job, I work as an consultant for various companies, and try to push the .NET stack as I can there, very successfully I might add. In one project, I even opted for a Razor Page setup, as the UI is quite simple and a SPA seemed like quite an overkill there ...

    In my side hustle, I am building a small travel focused application called Itsy. All backend fuctionality is handled by a .NET webapi, using Cloud Firestore from Google as the persistent database.

  11. 1

    Remotime is built using .NET for Android / iOS (Xamarin). Backend is using Azure Functions + CosmosDB.
    Lots of goodies to get excited about for .NET 6, esp performance + .NET MAUI :)

    1. 1

      Yeah, I am really excited about the performance updates in .NET 6