abp suite 2.9.0 Define Property no longer has a nullable check box + regex added. Where is that documented? How do I tag a property as nullable now?
Hi - I reported the same for the abp.io login. Looks like it's a framework issue also - so is it also broken in 2.9 and when is 3.0 scheduled for release?
yes - should be - how does bug tracking work on commercial? I'm used to Zero where we can track identified bugs to resolution/release.
Regards
Yes - Alper - nice and clear - please add to the official commercial documentation set (when you get a chance)
Regards,
yes - there were similar problems with zero (a while back) - I volunteer for 3rd party macOS testing if you need it...
Regards
hi alper - possibly a response to another ticket? this one has to do with abp suite migrations on the mac...
Thanks for looking into this.
I am new to abp.io and abp suite so bear with me : we did update (via abp suite) the easycrm 2.6 solution after abp suite update to the latest version 2.8. Seems like what you are saying is that application code needs to be updated - which is beyond the scope of abp suite. Am I correct?
Just want to understand what we can expect going forward if, for example , we develop on 2.8 and a new 3.x version of the framework and abp suite come out. Looks like abp suite solution update/upgrade only touches the npm and nuget packages.
Regards
yes - no doubt you are issuing the same CLI calls.
as stated above - your framework needs an appsettings.json in EFCore.DbMigrations for this to work on my side. Unless you are attempting to tool differently...
Hi alper - removed and re-installed abp suite and still getting the compilation warnings above. I think the warnigs have to do with obsolete methods and async methods lacking await operators - clearly something in (possibly) an earlier version of the application code. Warnings are in Pages/Entity/CreateModal.cshtml and Pages/Entity/Index.cshtml. These warnings don't occur on brand new 2.8 solutions (I tested that)
As I stated above the latest easycrm was based on 2.6 while the framework is now 2.8. Doesn't seem to be a show stopper but you may want to inform the developer(s) assigned to easycrm.
This is the latest easycrm (downloaded a few days ago) Looks like it was based on abp 2.6.2 I updated all npm and nuget packages -> all project files are 2.8.0 now
migrations and database updates don't work on macOS (see other ticket) so applied the changes manually
crud generator on easycrm works now
FYI - the (easycrm) code apparently needs an update too since I am getting these server warnings:
EntityFrameworkCore/EasyCrmDbContext.cs(14,7): warning CS0105: The using directive for 'Volo.Abp.EntityFrameworkCore.Modeling' appeared previously in this namespace [/Users/me/dev/aqua/abp-pro/easy-crm/src/Volo.EasyCrm.EntityFrameworkCore/Volo.EasyCrm.EntityFrameworkCore.csproj] Menus/EasyCrmMenuContributor.cs(3,7): warning CS0105: The using directive for 'Microsoft.AspNetCore.Authorization' appeared previously in this namespace [/Users/me/dev/aqua/abp-pro/easy-crm/src/Volo.EasyCrm.Web/Volo.EasyCrm.Web.csproj] EasyCrmWebModule.cs(226,13): warning CS0618: 'AbpAspNetCoreMvcApplicationBuilderExtensions.UseMvcWithDefaultRouteAndArea(IApplicationBuilder, Action<IEndpointRouteBuilder>)' is obsolete: 'Use app.UseConfiguredEndpoints(...) extension method instead!' [/Users/me/dev/aqua/abp-pro/easy-crm/src/Volo.EasyCrm.Web/Volo.EasyCrm.Web.csproj] Pages/Authors/CreateModal.cshtml.cs(24,27): warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread. [/Users/me/dev/aqua/abp-pro/easy-crm/src/Volo.EasyCrm.Web/Volo.EasyCrm.Web.csproj] Pages/Authors/Index.cshtml.cs(29,27): warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread. [/Users/me/dev/aqua/abp-pro/easy-crm/src/Volo.EasyCrm.Web/Volo.EasyCrm.Web.csproj] watch : Exited watch : File changed: /Users/me/dev/aqua/abp-pro/easy-crm/src/Volo.EasyCrm.EntityFrameworkCore.DbMigrations/Migrations/EasyCrmMigrationsDbContextModelSnapshot.cs watch : Started Menus/EasyCrmMenuContributor.cs(3,7): warning CS0105: The using directive for 'Microsoft.AspNetCore.Authorization' appeared previously in this namespace [/Users/me/dev/aqua/abp-pro/easy-crm/src/Volo.EasyCrm.Web/Volo.EasyCrm.Web.csproj] Pages/Authors/CreateModal.cshtml.cs(24,27): warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread. [/Users/me/dev/aqua/abp-pro/easy-crm/src/Volo.EasyCrm.Web/Volo.EasyCrm.Web.csproj] Pages/Authors/Index.cshtml.cs(29,27): warning CS1998: This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread. [/Users/me/dev/aqua/abp-pro/easy-crm/src/Volo.EasyCrm.Web/Volo.EasyCrm.Web.csproj] EasyCrmWebModule.cs(226,13): warning CS0618: 'AbpAspNetCoreMvcApplicationBuilderExtensions.UseMvcWithDefaultRouteAndArea(IApplicationBuilder, Action<IEndpointRouteBuilder>)' is obsolete: 'Use app.UseConfiguredEndpoints(...) extension method instead!' [/Users/me/dev/aqua/abp-pro/easy-crm/src/Volo.EasyCrm.Web/Volo.EasyCrm.Web.csproj]
