https://github.com/abpframework/abp/pull/13059
Hi @jlavallet,
As i see, these logs are harmless and the solution should be created successfully. You can continue development.
We'll try to remove these logs in the next patch version.
Hi @shobhit,
I've saved your feature request. We'll discuss and may include in next releases. Thank you for the feedback.
This is very interesting. See the source code https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.Cli.Core/Volo/Abp/Cli/ProjectModification/NugetPackageToLocalReferenceConverter.cs#L33
We use Directory.GetFiles(...) to find csproj files, and when we try to read one of them we shouldn't receive DirectoryNotFoundException. I don't understand why you are facing this issue.
However, i placed a File.Exist(...) check before reading a csproj file. See https://github.com/abpframework/abp/pull/12768
I'm closing the issue since it will be resolved with that pull request. If you continue to face this issue after stable 5.3 release, you can re-open.
Could you try the same process with CLI?
run this command to create the project:
abp new IWIT.BMSNext -u angular --separate-identity-server --preview
then move to aspnet-core folder and run:
abp add-module IWIT.BMSNext.Dictionary --new -t module-pro --add-to-solution-file
abp add-module IWIT.BMSNext.Basic --new -t module-pro --add-to-solution-file
Hi,
I can't reproduce the problem.
IWIT.BMSNext)IWIT.BMSNext.Dictionary)IWIT.BMSNext.Basic)It worked successfuly and i could build the whole solution.
Hi @alaa
Can you remove the project from suite, then delete bin/obj file folders, and add the project again?
I've created an internal issue about this.
We'll try to reproduce this problem and inform you.
I guess it is related with the naming but i couldn't reproduce.
Can you type the module names?
main solution: IWIT.BMSNext
first module: IWIT.BMSNext.Dictionary ?
second module: ?
Hi @kapil,
See https://select2.org/troubleshooting/common-problems#select2-does-not-function-properly-when-i-use-it-inside-a-bootst