Hi @serdar.genc@talentra.net, if you need to update the jquery version to 3.6.0, you can add a resolutions
section to your package.json file and specify the version of the package you want. Then run the yarn install && gulp
command on your terminal.
For more info about resolutions system of yarn, see here
{
"name": "Acme.BookStore",
"dependencies": {
//...
}
"resolutions": {
"jQuery": "3.6.0",
}
}
I will try your instruction.
After following the steps, you can close the question if it works, if you still got problem please don't hesitate to write back.
Hi @mc86, I watched your video and I noticed your ABP Suite and ABP project versions are different. (Suite runs in v5.0.0-rc.1 and your project created in v4.4.4)
( A screenshot from your video, 4:05) It used the cached template. (v4.4.4)
Please apply these steps:
1-) Ensure you've upgraded both CLI and Suite versions to 5.0.0-rc.1.
dotnet tool update Volo.Abp.Cli -g --version 5.0.0-rc.1
dotnet tool update Volo.Abp.Suite -g --version 5.0.0-rc.1
2-) Delete the microservice-pro template for v5.0.0-rc.1, if you've created yesterday. (Because we've updated ms-pro template for Blazor UI yesterday.)
(Delete this zip file: %UserProfile%\.abp\templates\microservice-pro-5.0.0-rc.1.zip
)
3-) Create a microservice template via CLI or Suite.
CLI:
abp new <solution name> -t microservice-pro -u blazor --preview
Don't forget to select "Preview" checbox.
4-) Then click the "Add an existing solution" button on homepage of Suite, and fill the input with your product-service path.
5-) Then click "Ok" button, and generate CRUD pages for an entity.
6-) Finally, click the "Save and generate" button and generate CRUD pages for your product-service.
After you've generated CRUD pages for your product-service, you will get the following error on your Blazor UI.
We've created internal issues for these problems and they will be fixed in the next release.
error CS0115: 'Books.OnInitializedAsync()': no suitable method found to override
For fix this problem, open your new generated file (Book.razor.cs in our case) change the namespace of the generated file.
Namespace should be MySptDemoForBz5001.ProductService.Blazor.Pages.ProductService
(add the folder name to end of the current namespace)
CreateBookAsync
and UpdateAsync
methods like in the image below.@mc86 I got your mail, I will watch the video and write you back asap.
HI @EngincanV did your try blazor ui? I capture my opreating screen in mp4,may I send to you?
Yes, I've tried Blazor UI and I could successfully generate CRUD pages.
You can send the video to engin.veske@volosoft.com.
Hi @mc86, I've tried just before. I could successfully generate CRUD pages and not encounter with any dependency resolution problem. But as @gterdem mentioned, i use the dotnet build /graphBuild
command in my root directory to ensure the solution is completely built.
Can you first execute the delete-bin-obj-folders.bat
file to delete all bin/obj folders that generated before and then run the dotnet build /graphBuild
on your root directory?
up to 5.0 rc1 also didn't work.as the same as4.4.4
ABP Commercial 5.0.0-rc.1 release has just been completed, so when you updated to 5.0.0-rc.1
it probably still used the v4.4.4 or it should have given some errors.
2.use "abp add-package Volo.Abp.Commercial.SuiteTemplates" in my blazor project. (if i don't use this i will get can't find Commercial.SuiteTemplates.dll error when generating
I've encountered this problem with MVC page generation, it really sometimes happen but after adding this .dll file into the relevant project directory, I could generate CRUD pages for MVC UI as well.
Hi @improwise, I've created an app-pro template with Blazor Server as UI and EF-Core as the database provider (in v4.4.4). Then, I could successfully generate CRUD pages for my Book entity.
For some strange reason, we notice that the error messages seem to be truncated.
Yes, I reproduced this problem using VS 2022. But there is not any problem, when using dotnet run
command or using other IDE such as Rider. There could be a problem in VS 2022, we will investigate this, thanks.
Hi @mc86, I will check and write you back asap.
Hi @mc86, after creating the new microservice did you follow the documentation?
After applyng the steps in the documentation you should be able to generate CRUD pages for your microservice.
Hi @LawrenceKwan, *.EntityFrameworkCore.DbMigrations
project is removed from the solution.
From v4.4.4 DbContexts are unified in the *.EntityFrameworkCore
project. (See the related issue)
*.EntityFrameworkCore.DbMigrations
project is removed and DbContexts are unified you can read this article.