Activities of "hillin"

Thanks Albert, I can see it's a good idea to set enum values. Can you have a look at the other issues described above?

With all these issues being said, I think the CRUD generator feature of abp suite is not really in a good shape, you have to be very careful and avoid some problematic features to get it working.

Some more minor problems:

• The enum members has to have values, otherwise the generated angular proxy is incorrect:

public enum MyEnum 
{
   Value1,
   Value2,
}

turns into

export enum MyEnum 
{
   Value1 =,
   Value2 =,
}

• Does not work with C#10 File-scoped namespace declaration, the generated DbContext will be broken

After unchecking the Create unit & integration tests option for the entity, generating the entity still reports the same error:

Error occurred on DB migration step! Make sure the project is compiled and working. Command output: Build started...
Build failed. Use dotnet build to see the errors.

However dotnet build runs just fine!

Edit: this one is because the aspnetcore project is running (without debugging). Closing the running project and finally the generation worked.

After replacing the enum property with an int type, generating the entity reports the following error:

Error occurred on DB migration step! Make sure the project is compiled and working. Command output: Build started...
Build failed. Use dotnet build to see the errors.

Turns out the generated EntityRepositoryTestsclass in the EntityFrameworkCore.Tests project, and the EntityApplicationTests class in the Application.Tests project does not compile. They have an excessive %%class-attributes%% text generated above the class signature. E.g.:

namespace MyProject.Entities
{   %%class-attributes%%
    public class EntityRepositoryTests : MyProjectEntityFrameworkCoreTestBase
    {

After removing the xmldoc and try to save and generate the entity, abp suite reports:

Cannot populate enum localizations! Error code: EN0004. System.NullReferenceException: Object reference not set to an instance of an object.
   at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Commands.EntityGenerateCommand.Qu5cDTUwlI()

Thanks @muhammedaltug, uninstalling node 16 and replace it with node 14 instead did the trick.

True, but I can still see their namespaces in the intellisense popup, that's the concern here. I'm totally okay that you obfuscate the classes, but please leave the namespaces alone.

Oh I forgot to mention it was ReSharper's intellisense popup. I haven't checked if the default intellisense shows them. For now the workaround is to disable namespace suggestions in ReSharper's intellisense settings, which obviously is not a smart idea.

It's not about what class (in the commercial assemblies) to use. As soon as any of these assemblies is referenced in my project, their obfuscated namespaces contaminate the intellisense popup, they appear whenever I type any code.