@Anjali_Musmade
That is NOT correct as I have working projects created during my trial before purchasing Personal license both created and now running and working using exactly the same string....
"ConnectionStrings": { "Default": "Server=(LocalDb)\MSSQLLocalDB;Database=AbpSolution_test;Trusted_Connection=True;TrustServerCertificate=true"
String being correct is confirmed as running below commands worked fine and project then runs...
Create migrations using the EF Core global tool by running "dotnet ef migrations add Initial_Migration" and appy migrations using "dotnet ef database update" commands. Finally run "dotnet run --migrate-database" command to migrate the database.
Logs files for both Studio and CLI available here - couldn't see way to attach to post...
thanks for confirming, that does make it difficult to do much customization then, so thank you for sending me the code
Gives me error below:
[10:22:11 INF] Downloading source code of Volo.Abp.Account.Pro (Latest) [10:22:11 INF] Output folder: C:\Users\User [10:22:12 ERR] Downloading source code failed for: Volo.Abp.Account.Pro Volo.Abp.Studio.AbpStudioException: Exception of type 'Volo.Abp.Studio.AbpStudioException' was thrown. at async Task Volo.Abp.Studio.Modules.Installing.SourceCodeDownloader.DownloadSourceCodeAsync(string moduleName, string targetFolder, string version, bool includeNightly) at async Task Volo.Abp.Studio.Cli.Commands.StudioGetSourceCommand.ExecuteAsync(CommandLineArgs commandLineArgs) at async Task Volo.Abp.Studio.Cli.StudioCliService.RunInternalAsync(CommandLineArgs commandLineArgs) at async Task Volo.Abp.Studio.Cli.StudioCliService.RunAsync(string[] args)
Thanks for email.
According to FAQ, Account Pro IS included in Personal License. But yes I see source code is not, which does make customizing ABP a lot harder, so thank you
{email removed}
Thank you, much appreciated :)
Okay thanks, I was running the command within Visual Studio terminal rather than ABP Studio, perhaps that is why it didn't update the file and I had to do it, but good to know.
Thank you, that was what I was checking, because when you run command manually (e.g. Studio not doing it during project creation) then it **doesn't **update that file and i had to do it manually before it would work