Hi, EngincanV Sorry, but I can not understand what do you mean by "the project that you shared is suppose to use central package management" I just did all steps as described in my previous comment https://abp.io/support/questions/9023/Can-not-add-Entity-to-Main-solution#answer-3a18e527-ce86-9cfe-f7fb-9d08e70d2bae
I got build error as described in step 6 so did zip full folder and shared it with you. What do you mean by "please fix the central package management problem"? I am not using any "central package management" just ABP Studio.
When i download your project and star investigating then I see build errors which explicitly says they are related to the "central package management" rather than the generated code.
So it seems that you either updated your solution to manage your package dependency from a single point or templates that you used is corrupted.
So, can you confirm that the project you shared was the right project and you created a startup template and then applied the provided steps? (Because something is not right in your project :))
Hi, EngincanV
Sorry for pushing.. any news?
Hi Viktor, sorry for the late response. I've checked your project, but it seems the project that you shared is suppose to use central package management, however there are some problems when building the application. So it seems the package versions are still being used in several project instead of a central place.
So, please fix the central package management problem and re-share your solution. So, I can directly focus on the problem that you are facing.
Regards.
Hi @cangunaydin, thanks for the detailed step-by-step explanation. I'll try it and write you back asap.
I have successfully converted. Here is the code for anyone who needs it: https://nguyendigital.net/migrating-mongodb-guids-from-legacy-to-standard-format-in-abp
Finally, thank you ABP so much for the help these past 2 days.
Thanks for sharing your steps and nice words. Closing the issue since your problem is resolved. Feel free to open it if there is any problem related to this ticket.
Regards
I think the best way is from the current database we will create a new one to get the data to be compatible with the structure of mongo v3 but it will be a bit complicated. I wonder if there is a better solution?
Actually, if you are building your application relatively new and your data is not important at the point, it's the easiest way as you said. If you need another solution, I need to know more details such as properties in the related entity, your custom implementation if there is any, etc.
Please help me. Because I tried the same as you but completely different.
- volo.abp.leptonxtheme.management.domain.shared not found
- Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX is available
Hi @nguyendigital, thanks for reporting the problem. We have published the related NuGet packages; however, we should have configured them on our side to let our customers use them. Now, we made the necessary change, and you should be able to access to the related NuGet packages.
Please let me know about the status. Your ticket has been refunded btw. Regards.
Thank you. It worked
Great to hear that. Regards.
I wander how this line works serverBuilder.AddProductionEncryptionAndSigningCertificate("openiddict.pfx", "00000000-0000-0000-0000-000000000000"); since this openiddict.pfx file is ignored from git (i.e: it doesn't exist on ther server)!!!
Hi, you can remove it from .gitignore if you wish or run the following command on your server to have this file:
dotnet dev-certs https -v -ep openiddict.pfx -p 00000000-0000-0000-0000-000000000000
https://abp.io/docs/latest/deployment/configuring-openiddict
Hi, EngincanV We are blocked with our solution due to this issue. Any updates on this?
Hi, I got your solution. But haven't had time to examine it yet. I'll check it asap.
Hi, the package Volo.Abp.Studio.Extensions.StandardSolutionTemplates is used by ABP CLI and ABP Studio to provide solution templates. Are you trying to install it manually? It's recommended to let ABP Studio CLI or GUI handle the installation for you. (This is not a package that can be used in your own applications)
I initially tried running the CLI tool to create a new tiered MVC solution and the error was thrown. I then checked via a manual install in VS Studio and was unable to install the package due to a missing nuspec file. It seems ABP Studio was unable to install the package by itself.
Okay, thanks for the explanation. Can you please try to clear your NuGet cache locally (by using the below command) and then try to open ABP Studio, or run an ABP CLI command?
dotnet nuget locals all --clearABP Studio CLI & GUI, uses the local cached NuGet package to seamlessly work. So, clearing the cache and re-installing the extension probably will fix this problem.
Thank you - this resolved the issue.
Great to hear that. Regards.
