(bug, Guidance2022.2.1.12-rc1): strange namespace when adding an EF Core database or Hangfire project

[vvdb-architecture]

When you add an EF Core database project, for example:

The resulting namespace previously was `TestFlow.Service.Database but it's now:

namespace EG.TestFlow.Service.Database;

public partial class DatabaseContext : DbContext
{
    public DatabaseContext(DbContextOptions<DatabaseContext> options) : base(options)
    {
    }

    protected override void OnModelCreating(ModelBuilder modelBuilder)
    {
        //Custom code conventions in OnModelCreating
        //define the default schema
        modelBuilder.HasDefaultSchema("app");

    }

}

A similar remark is valid for Hangfire projects. Why the EG-prefix? This shouldn't be necessary.

[GFlisch]

In all the code generated, the namespace contains the company. It has been decided to use EG for Elia Group. This is a config update => This is a company choice. What do you want EliaGroup, Elia,...