Hi, I created a project from your template in ASP.Net Core and Angular 2, including the Module Zero, around 2 weeks ago. Today I noticed in the NuGet Package management that I can upgrade both Abp.Framework and Abp.Zero.Framework from 1.5.1 to 2.0.2 version. Once I did that I got lots of errors and bugs almost everywhere within all defined projects! I had a brief look at the errors, and most them were about some changes in the constructors and other methods signitures. When I downgrade them both to their original versions, all errors disappeared. So here are my wonders:
- Was it the proper way that I have upgraded the dlls?
- I noticed a project named as Migrator within the generated solution. Should I have upgraded them though that? If yes, how? if No, what it is all about?
- If we are supposed to alter the code manually after each upgrade, is there any details in your website on what have changed and what specifically should be changed, from what to what?
- Does the created project work with Entity framework Core(7.0) or it still use Entity framework 6?
- The Entity framework DB commands do not work in the Package Manager Console (I am selecting EntityFramework project as of the default project drop down value). The error says: "The EntityFramework package is not installed on project". I am able to execute the commands from the Windows CMD though!
Regards
3 Answer(s)
-
0
Hi,
1-2 Yes, you can update all abp.* packages from nuget. And also you get some errors and these errors are not major breaking changes. You can fix these errors easly.
Yes, both aspnet-zero and aspnet-boilerplate projects have documents about changes (we dont write any document about breaking changes if they are not major). <a class="postlink" href="https://github.com/aspnetboilerplate/aspnetboilerplate/releases">https://github.com/aspnetboilerplate/as ... e/releases</a> <a class="postlink" href="https://aspnetzero.com/Documents/Change-Logs">https://aspnetzero.com/Documents/Change-Logs</a> <a class="postlink" href="http://volosoft.com/net-core-support-for-asp-net-boilerplate-and-asp-net-zero/">http://volosoft.com/net-core-support-fo ... -net-zero/</a>
Latest projects are working with Entity framework Core. <a class="postlink" href="http://volosoft.com/net-core-support-for-asp-net-boilerplate-and-asp-net-zero/">http://volosoft.com/net-core-support-fo ... -net-zero/</a>
EF commands work in Package Manager Console. Before you run the command, you should set Mvc or Host project as startup page.
I hope this helps.
-
0
Thanks for your response. With regard to the number 5 (5. The Entity framework DB commands do not work in the Package Manager Console (I am selecting EntityFramework project as of the default project drop down value). The error says: "The EntityFramework package is not installed on project". ):
I have installed EntityFramework and now receiving the following error: "No DbContext was found in assembly 'Parking.EntityFramework'. Ensure that you're using the correct assembly and that the type is neither abstract nor generic." As you have you advised I have set the startup project and have selected the EntityFramework for the Default project in the Package Console Manager
-
0
Hi @zokho,
Sorry for the late reply, have you fixed your problem ?
