ABP Framework version: v4.4.2 UI type: Blazor DB provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): no
Exception message and stack trace: The project name is invalid! Please specify a different name. Volo.Abp.Cli.CliUsageException: The project name is invalid! Please specify a different name.
Steps to reproduce the issue:
It seems like it is impossible to create a new project/SLN in ABP Suite that contains/ends with "Blazor", like "TestProjectBlazor". Generating the project online with the same name and then open it in ABP Suite seem to work though. No problem creating something like "TestProjectAngular".
Had a quick look and it seems like there are few resons not to use the ABP Suite instead assuming you have access to it of course.
Hi,
Redis is the most popular cache server. It has undergone a lot of tests and has extremely high performance and stability. so this is why we choose to redis.
Memurai seems good, you can also try to use it, the code does not need any changes, because it is fully compatible with redis
Thank you.
Hi,
To improve performance, we cache permissions and settings etc, so we need distributed caching to keep public and back-end website data consistent.
Thanks, but that isn't really an answer to why the choice was made to go with Redis in particular, just why caching in general is a good thing.
Related question, should we consider using something like Memurai instead which seems to run natively on Windows?
https://www.memurai.com/
I should perhaps add that we have been able to install and configur Redis on a development machine and it seem to be working so this is more a question of WHY than HOW.
For anyone reading this interested in the HOW:
https://developer.redis.com/create/windows/ https://redis.com/blog/redis-on-windows-10/
Thanks.