Activities of "fncoph"

Hi @ismcagdas,

We're fairly only following the pipeline instructions from this page: https://docs.aspnetzero.com/en/aspnet-core-mvc/latest/Setting-Up-an-Azure-Pipeline-Mvc-Core#additional-pipeline-steps-for-the-mvc-project

Since we're getting this error below, so I tried some other workarounds and see if it works.

2020-09-09T14:35:54.4340623Z ##[error]The process 'C:\hostedtoolcache\windows\dotnet\dotnet.exe' failed with exit code 1
2020-09-09T14:35:54.4532215Z ##[section]Finishing: Generate Migration Scripts

Already got the answer. Sorry for the trouble.

src\proj.Core\DynamicEntityProperties\AppDynamicEntityPropertyDefinitionProvider.cs , you can add the entities below the default User class

Hi @ismcagdas,

I think @christianharo means is that can we add a new dynamic entity aside from user only, and how do we enable this on our newly created entities?

For example, if I want to assign a supported language for our customers, I want to assign a multicheckbox dynamic parameter to my customer entity.

Hi,

This is the last run setting for Migration Script

I even tried checking the "install dependencies for .net 3.0", but same result. Already tried switching from different agent spec as well.

Before GMS, I tried to run command below using command prompt: dotnet tool install --global dotnet-ef

Thank you

Hi, Thank you so much for the reply. I have followed as you instructed. SameSiteHandlingExtension.cs

Web.Mvc

Web.Host

I even tried commenting the env.IsDevelopment condition as per @serdar said, but to no avail. I am not really sure what to do at this point as we cannot start anything without resolving it first. Thank you very much.

Hi @serdar, Thank you so much for your response. I have modified the same as you have provided, but to no effect. Here is my current setup:

Hi, I have done the same direction above, and login functionality is still elusive. Any other setup we need to do to get this through?

Hi,

I have the same problem, too, after testing the latest demo source code in our local environment. I hope you can send an immediate patch for this, because we cannot start our testing due to this persistent problem. Thanks