Activities of "improwise"

I think using a script is more convenient than using Visual Studio, but I'll take a look.

Yes, agreed, but with the "Docker" file being there, it would be good if it was setup for VS. Not sure if that file is actually ever used or just the Docker.local?

The Docker files (ie not Docker.local) are not recognized by Visual Studio, probably because they are not added to the project in the correct way. This means that the Docker functionality in Visual Studio isn't there for publishing etc. as to VS, there exist no Docker files. While you can of course to this yourself, I think it would be nice if it was setup correctly from start, not sure how much extra work it would mean though to get it working with Docker Compose etc.

The health check for SQL server in YAML file will fail

healthcheck: test: /opt/mssql-tools/bin/sqlcmd -S sql-server -U sa -P "myPassw0rd" -Q "SELECT 1" -b -o /dev/null

This both because the sqlcmd seem to have moved to /opt/mssql-tools18/bin/sqlcmd and also as i lacks the -C to accept self signed certificates.

https://github.com/testcontainers/testcontainers-dotnet/issues/1220

Some other improvements

  1. User SQL Server 2022 instead of 2019 unless there are a good reason for it
  2. User "docker compose" rather than "docker-compose"
  3. Probably some other dependencies like Redis etc that should be updated to newer/latest version

docker-compose.yml still uses

version: '3.8'

which is deprecated (the version attribute that is)

There is a small bug in the build-images-locally.ps1 file, at least for Angular:

Write-Host "********* BUILDING Angular Application *********" -ForegroundColor Green $angularAppFolder = Join-Path $slnFolder "../angular"

This should be ./angular with only one dot as above it, you already have the lines

$currentFolder = $PSScriptRoot $slnFolder = Join-Path $currentFolder "../../"

Or the script wont find the folder (at least assuming you follow the instructions "Navigate to etc/docker-compose folder and run the build-images-locally.ps1 ").

Reopened once again.....

It seems when using the Angular UI and creating Navigation properties, ABP Suite tries to invent the type "Guid" in Angular/Typescript even though that does not exist (at least not by default). If you change it to string it will work both development time and run time it seems.

Is any action being taken on this? It seems like we rarely get feedback on bugs etc reported in this thread compared with when creating new ones, but then general threads like this seems kind of pointless. Thanks.

Hello,

Which version does your app use? Also on which page did you test this? When I test it on the Tenants page, I get a result like below:

Using latest version of ABP Suite to generate Angular components/pages and they all have this problem still.

@liangshiwei

Showing 31 to 40 of 313 entries
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v10.1.0-preview. Updated on October 21, 2025, 11:36