What is the projected timeline, planned is a very brought statement.
Thanks, that will work for us ;-)
Will you continue to support the old CLI? Or is this something that will disappear?
See my answer above.
This works for the moment: dotnet tool install -g Volo.Abp.Cli As it installs the latest (old) CLI.
Also tried with the --old switch, but that resulted in an error as well
I'm getting a message saying that I need to open the browser to login, but since this jobrunner is a standard devops agent, that is not possible
Oh, but you didn't answer my question :-) Where should this code go? In each specific file? Can you please give an example?
ah OK. Thanks. We will upgrade soon.
Hi,
Is there a specific reason why the initial catalog is replaced by master? in the connectionstring checker? https://github.com/abpframework/abp/blob/b23affb0ed225f020dc7b66aebc208acd71a1c01/framework/src/Volo.Abp.EntityFrameworkCore.SqlServer/Volo/Abp/EntityFrameworkCore/ConnectionStrings/SqlServerConnectionStringChecker.cs#L20-L21
Managed identities should not have access to master, they are database scoped credentials and only need to have access to the Database (or Initial Catalog) passed in the connectionstring.
Hi,
We are sending our errors to Azure Application Insights, so we don't have a logfile.
BUT, it's even more weird: The test actually fails, but when hitting save, the database gets created. So there is definitely something wrong with that connection string check that doesn't take into account valid connectionstrings using Managed Identity syntax.
