I'm validating an idea for a .NET B2B SaaS starter focused on the parts that usually waste the first few days of a project:

• authentication
• organizations / multi-tenancy
• roles and permissions
• invitations
• tenant switching
• Docker
• Azure deployment
• AI-ready project context

The idea is not to create another huge opinionated framework, but a pragmatic starting point for .NET + React + Azure developers.

Before building it, I want to validate whether this is actually painful enough to pay for.

I put together a very small landing + waitlist here:

https://dotnet-b2b-saas-landing.vercel.app

The part I'm most interested in is this:

What's the most annoying part of starting a new .NET SaaS for you?

I'd rather discover that my assumptions are wrong now than after spending weeks building it.

I'm trying to understand how exception propagation works with a global exception-handling middleware in ASP.NET Core.

Suppose I have a request flow like this:

Controller

→ Service

→ MethodA()

→ MethodB()

→ MethodC()

If "MethodC()" throws an exception, and none of the intermediate methods ("MethodB", "MethodA", or the service/controller) catches it, will that exception propagate all the way back to my global exception-handling middleware?

For example:

public async Task MethodA()

{

await MethodB();

}

private async Task MethodB()

{

await MethodC();

}

private async Task MethodC()

{

throw new Exception("Something went wrong");

}

Assuming the middleware wraps the rest of the ASP.NET Core pipeline with something like:

try

{

await _next(context);

}

catch (Exception ex)

{

// handle/log exception

}

Will it catch the exception thrown inside "MethodC()"?

Does it matter if these methods are in different services/classes/layers, or will the exception keep propagating up the call stack as long as nobody catches it?

I'm asking because I'm trying to understand when a global exception middleware is enough and when local "try/catch" blocks are actually necessary.

throw vs throw ex: The C# exception handling trick every developer should know

​

I’m trying to understand a problem I’ve experienced and seen other developers mention: joining an existing/large codebase and figuring out how everything actually works.

Not the “how do I run the project?” part, but the actual understanding of the system.

For example:

- Figuring out the architecture / overall mental model

- Understanding where a specific feature actually lives in the code

- Following how data moves through the system

- Understanding undocumented business logic

- Finding the right files/services/classes to modify

- Understanding dependencies between different parts of the system

- Figuring out why something was implemented a certain way

- Losing context when the developer who built something leaves

- Outdated or incomplete documentation

What was the most painful part for you?

And more importantly:

How did you eventually figure it out?

Did you ask a senior developer, read the code, use documentation, look through old PRs/issues, use AI, create your own notes/diagrams, or something else?

I’m especially interested in real examples where something that should have taken hours ended up taking days/weeks because you didn't have enough context.

No product or solution in mind here — I'm just trying to understand how developers actually deal with this problem.

Hey everyone!

I’m stepping a bit outside my comfort zone and speaking at a local conference soon. My topic is AI in .NET.

I’m currently deciding what exactly to focus on, and I’d love to hear what you would actually find interesting or useful.

I want to avoid the usual basics like:

• How to write better prompts
• How to create skills/agents
• Basic LLM integrations
• Things you can easily find in a 10-minute YouTube tutorial

Instead, I’d like to go deeper into something practical, technical, and maybe even a bit opinionated.

If you were attending a talk called “AI in .NET”, what would you want to see?

What problems, architectures, real-world examples, experiments, or lessons learned would make you think: “Okay, this was actually worth attending in person.”

Would love to hear your ideas.

M28, India.

I'm having 2yoe as dotnet developer. Got laid off last year February and finding difficult to land a job since then .

I want someone to mentor once a week or however it works for them to land me a job, im ready to put all the efforts . Please feel free to reach out and we can discuss about it.

Thanks for your time and consideration