---
uid: whats-new.2025.04
---
# What's new in Intent Architect (April 2025)

Welcome to the April 2025 edition of highlights of What's New in Intent Architect. Here's a roundup of the latest updates and improvements.

- Highlights
  - **[Expose Commands/Queries/Services as gRPC Endpoints](#expose-commandsqueriesservices-as-grpc-endpoints)** - Easily expose services over gRPC which will generate all the necessary `.proto` files and gRPC service implementations.
  - **[Ocelot API Gateway Modeling](#ocelot-api-gateway-modeling)** - Model your API Gateways for routing requests or setting up a lightweight BFF using Ocelot.
  - **[Central Package Management Enhancements](#central-package-management-enhancements)** - Gain greater control over the output location of the `Directory.Packages.props` file.
  - **[SQL Importer Trigger Awareness](#sql-importer-trigger-awareness)** - When using the [SQL Server Importer](https://docs.intentarchitect.com/modules-dotnet/intent-sqlserverimporter/intent-sqlserverimporter.html) triggers are now detected and modeled in the Domain Designer.
  - **[Data Contract Attribute Naming Customization](#data-contract-attribute-customization)** - Data Contract attribute names can now be customized to align with the SQL column name.

## Update details

### Expose Commands/Queries/Services as gRPC Endpoints

Our new module allows exposing Services Operations, Commands and Queries over [gRPC](https://grpc.io/) using the [Grpc.AspNetCore NuGet package](https://www.nuget.org/packages/Grpc.AspNetCore).

In the same way you would expose an HTTP Endpoint for WebApi, simply use the context menu option to expose a Command, Query, Service or Operation as a gRPC endpoint:

![Expose as gRPC Endpoint context menu option](images/expose-as-grpc-endpoint-context-menu-option.png)

The module will generate `.proto` files, service implementations to dispatch the endpoint and all relevant mapping logic to convert incoming and outgoing protocol buffers to and from DTOs/Commands/Queries.

Additional information available [here](https://docs.intentarchitect.com/modules-dotnet/intent-aspnetcore-grpc/intent-aspnetcore-grpc.html).

Available from:

- Intent.AspNetCore.Grpc 1.0.0-beta.0

### Ocelot API Gateway Modeling

Model your API Gateways for routing requests or setting up a lightweight BFF using [Ocelot](https://ocelot.readthedocs.io/en/latest/introduction/bigpicture.html).

![Ocelot API Gateway modeling](images/ocelot-modeling.png)

Reference your Intent Architect application which holds the API endpoints you wish to cover with an API Gateway then create the API Gateway Routes that holds Route Associations to those endpoints.

Additional information available [here](https://docs.intentarchitect.com/modules-dotnet/intent-apigateway-ocelot/intent-apigateway-ocelot.html).

Available from:

- Intent.ApiGateway.Ocelot 1.0.0-beta.2

### Central Package Management Enhancements

When `Central Package Management` is enabled in a solution, the output location of `Directory.Packages.props` can now be explicitly specified or automatically detected based on the location of an existing file.

![Central Package Management Enhancements](images/cpm-updates.png)

Additional information available [here](https://docs.intentarchitect.com/modules-dotnet/intent-visualstudio-projects/intent-visualstudio-projects.html#central-package-management).

Available from:

- Intent.VisualStudio.Projects 3.8.10

### SQL Importer Trigger Awareness

When using the [SQL Server Importer](https://docs.intentarchitect.com/modules-dotnet/intent-sqlserverimporter/intent-sqlserverimporter.html) to import an existing database schema into Intent Architect, tables and views with defined triggers will now be correctly identified and marked accordingly.

![Trigger Import](images/trigger-import.png)

Additional information available [here](https://docs.intentarchitect.com/modules-dotnet/intent-sqlserverimporter/intent-sqlserverimporter.html#trigger-imports).

Available from:

- Intent.SqlServerImporter 1.1.1

### Data Contract Attribute Customization

The `Column` stereotype can now be applied to `Data Contract Attributes` and realized in code, enabling SQL column names to differ from the modeled names for modeled stored procedures.

![Data Contract Attribute](images/data-contract-attribute.png)

Available from:

- Intent.Entities 5.1.11-pre.0