Activities of "alper"

Issue:

The issue raises after .NET 6 migration. There's a new feature that blocks multiple files to be copied to the same target directory with the same file name. See https://docs.microsoft.com/en-us/dotnet/core/compatibility/sdk/6.0/duplicate-files-in-output

Solution #1 (workaround):

You can add the following build property to all your publishable (*.Web) projects' *.csproj files. This property will bypass this check and works as the previous .NET5.

<ErrorOnDuplicatePublishOutputFiles>false</ErrorOnDuplicatePublishOutputFiles>

Solution #2:

Exlude the problemmatic files to be copied to the output folder. In this example we'll exclude these files: compilerconfig.json and package.json Add the following lines to your common.props (located in the root directory of your solution)

<Content Remove="compilerconfig.json;package.json"/>
<None Include="compilerconfig.json;package.json">
  <ExcludeFromSingleFile>true</ExcludeFromSingleFile>
  <CopyToPublishDirectory>Never</CopyToPublishDirectory>
</None>

Only the following cases enforces license check

• Debugger attached
• ASPNETCORE_ENVIRONMENT = Development

I see that you already updated your ASPNETCORE Environment variable. There's only 1 possibility left, you are attached a debugger to the project. Are you running the container from Visual Studio with debugger attached? To check this add the following command to your Program

Console.WriteLine("DebuggerAttached: " + System.Diagnostics.Debugger.IsAttached);

Did you add the Volo.Saas module with source-code? If yes, did you compile it in debug mode?

Public classes are not being obfuscated. Those are private and protected ones which you'll not use.

a

a

is it possible to share your project with us? info@abp.io

and be aware that the first run of DI takes the longest time (initialization of services) the consistent test can be done after 2nd or 3rd request.

results are not consistent. are you running the server-side on your machine or on a cloud service?

which class are you trying to use ?

Sorry but Blazor is a keyword being used in Suite template replacer. When you use the keyword Blazor, you may have some compile issues in Blazor project. So you specify a different name (Blazzor)