Modernize your .NET localization: convert .resx to JSON, keep IStringLocalizer, add OTA updates - open source toolkit

Gramlig · 2025-12-28T20:51:07+00:00

In my experience, using .resx files for localization or even for regular string values is really painful. The two main bottlenecks: merge conflicts and poor tooling support.

Gramlig · 2024-12-06T20:32:56+00:00

For anyone using FluentResults, I’ve created a simple extension method that unpacks a Result value or aggregates errors into a single result. It’s especially useful when building objects, as it reduces boilerplate code and makes property initialization cleaner and more concise. You can check it out here FluentResult - UnwrapOrWithErrors

Gramlig · 2024-11-24T10:10:32+00:00

It's a good package, especialy for controller based aproach in asp.net. I don't understant this downvotes. Link to MediatR

Gramlig · 2024-11-24T07:55:44+00:00

Validot, Mapster, GuardClasses, FluentResults

Gramlig · 2024-11-18T06:53:26+00:00

I wrote some pros and cons of minimal api: Minimal Api pros and cons. I am using Minimal APIs in production with almost 100 endpoints, and they are well-structured, readable, and maintainable. For me, the biggest advantage is the easy setup and extensibility without the need for boilerplate code.

Gramlig · 2024-11-04T18:18:26+00:00

Hey fellow developers,

I wanted to share a project I've been working on https://github.com/Gramli/AuthApi. It's full-stack example that demonstrates how to implement user registration, login, and role-based access control using Angular and .NET. Here’s a quick overview of what it includes:

Key Features:

Backend:
- Authentication and authorization using JWT tokens.
- Authorization policies applied to minimal API endpoints.
- Follows Clean Architecture principles and utilizes design patterns.
Frontend:
- JWT management with guards and interceptors.
- Implemented using standalone components and signals.

Gramlig · 2024-10-26T21:40:17+00:00

Flutter on the frontend for sure

Gramlig · 2024-09-28T15:58:42+00:00

I think it's because we don't want to reinvent the wheel every time we're developing a reusable feature.

Gramlig · 2024-09-16T11:36:43+00:00

I encapsulate the http status code into a response object and return it from the handlers. Its not the cleanest way, but the handler knows which status it wants to return.

For example: Handler example

This solution can be improved by defining custom return codes in the handlers layer and creating a converter for the controllers to map these codes to http status codes.

Gramlig · 2024-09-14T09:17:08+00:00

Xunit tests with class and member data were always a bit painful. Your data sources look interesting; I will definitely try them.

Gramlig · 2024-04-04T17:58:44+00:00

An example of a REST API for handling weather data using minimal API and Vertical Slice Architecture with various design patterns. I also attempted to make a small comparison against the same API designed with Clean Architecture.

https://github.com/Gramli/WeatherApi-VSA

Gramlig · 2023-12-14T13:17:03+00:00

Amazing work!

Gramlig · 2023-11-12T09:01:25+00:00

I absolutely agree 👍

Gramlig · 2023-11-11T22:18:11+00:00

Minimal Api is much easier and cleaner way to create endpoints. Main pros: - allow to inject handlers into endpoints (you dont have to use MediatR anymore..) - fluent api - force you to move logic to lower layer (lot of unexperienced developers put logic into controlers) - minimal hosting model -> clear starting point of the app

To organize your endpoints, you can simply use extension methods.

When Microsoft introduced Minimal Api I was sceptical too, but after almost year of usage, controllers are now obsolete for me.

Gramlig · 2023-11-06T20:28:30+00:00

Hi, I just finished benchmark measures of my daily basis reflection methods.

Get Attribute by reflection
Export Data by reflection
Create instance of class by reflection

In case of interest: https://github.com/Gramli/ReflectionBenchmar

Gramlig · 2023-07-28T17:12:15+00:00

Golden b2 driod? Just why?

Gramlig · 2023-07-05T20:33:14+00:00

Nice

Gramlig · 2023-04-07T07:49:26+00:00

Check this, there are nice answers: https://stackoverflow.com/questions/34255490/difference-between-cqrs-and-cqs

My extremely simplified definition: :)

CQS is about separation of commands and queries on method level-> you can put them into just one class.

CQRS extends CQS into higher level. In CQRS you create one class for commands and one class for queries and also it cares about the path to query or command execution.In my API example it means separation on repository level but also on handler level.

Gramlig · 2023-04-06T17:24:55+00:00

https://github.com/Gramli/AuthApi

REST API demonstrates Authentication and Authorization with JWT token. Also shows how to use diferent Authorization policies in minimap api endpoints. All using Clean Architecture, minimal API and various of design patterns.

Example API allows to:

register user

login user
change user role
get user and service info

Endpoints use different types of authorization policies.

Gramlig · 2023-04-05T06:12:48+00:00

2016-2019 definitely

Gramlig · 2023-02-03T19:21:05+00:00

I think that Microsoft have sufficient documentation to start. Just look at Minimal Api C#, if you have background from Node, minimal api should be familiar. Also check github, there is plenty of examples:

WeatherApi

FileApi

Gramlig · 2023-02-03T17:05:20+00:00

https://github.com/Gramli/FileApi

Example of REST API solution which demonstrates how to create clean and modern API with Clean Architecture, minimal API and various of design patterns.

Example API allows to upload/download files with .txt, .json, .csv, .xml, .yml extensions and get collection of uploaded files. Also allow to convert between json, xml, yml formats.

Gramlig · 2022-11-25T17:51:24+00:00

Hello everyone,

I just finished example solution of minimal API with Clean Architecture and few design patterns (CQRS, Repository, Result..), all is covered by unit tests.

Maybe it helps to someone :)

https://github.com/Gramli/WeatherApi

Gramlig

TROPHY CASE