Hi abp suite 2.9 version will be released today

ABP Framework version:** v2.9.0 Would you please provide guidance on why I am unable to install ABP Suite

Step 1: dotnet tool install -g volo.abp.cli (Success) Step 2: abp login -p (Success) Step 3: abp suite

Unable to install ABP Suite

* https://commercial.abp.io/tools/suite * https://docs.abp.io/en/commercial/latest/abp-suite/index

Remove ABO Suite: abo suite remove 2. Delete Suite folder: c:\users\username\\.abp\suite 3.

Install ABP Suite: abp suite install

@edirkzwager, I don't see where you deleted the abo suite folder c:/users/username/.abp/suite Make

sure you delete that folder before trying to install abp suite.

ABP Suite should not allow an Entity to contain a Property with the same name. !

Update the ABP CLI: `dotnet tool update -g Volo.Abp.Cli` Update the ABP Suite: `abp suite update`

Create new project with Abp suite choose Angular\, Mobile:None\, DatabaseProvide:EF Core and seperate

Add Identity Module from Abp suite and choose "Add as project"\.

Hi Mehmet Yes we did, we used ABP Suite 2.8 to do the update.

We updated our aspnetcore to 2.8 using ABP suite 2.8.

open ABP Suite ``` abp suite ``` !

Hi - this is a brand new commercial solution and the suite is up to date (v2.8).

**looks like there are definitely some tooling issues with abp suite migrations (at least on the mac)

Hi - any news on this : migrations and database updates from abp suite dont' work on macOS. Regards

this one has to do with abp suite migrations on the mac...

Windows uses `"\"` and MAC `"/"` that's why Suite cannot change directory correctly.

abp suite crud generator error : MSB1009 error occured on DB migration

The DTO's generated via ABP Suite is located in `*.Application.Contracts` project.

If you created it via Suite, it creates the entity DTO files in `Acme.BookStore.Application.Contracts

If you name it AppUser then Suite generates `AppUserDto` and it's being used in `IAppUserAppService.cs

First of all, ABP Suite asks you a `DTO` of the dependent entity.

ever use the ABP Suite Navigation Properties if we what to follow the DDD best practice.

After creating the Ticket entity with ABP Suite, I added ``` .UseIdentityColumn(1000, 1); ``` to the

@roop.yekollu, can you run `abp suite remove` then `abp suite install`

**, and then **abp suite install** and received the same result.

Remove ABP Suite: **abp suite remove** 2. Delete Folder: `C:\Users\Username\.abp\suite` 3.

if you have updated Suite on 2020-05-21, please remove and install it again. ``` abp suite remove abp

suite install ```

Update the ABP CLI: `dotnet tool update -g Volo.Abp.Cli` Update the ABP Suite: `abp suite update`

I have created a simple application with abp suite to test and solve your problem and I had no errors

The rest of code of applicaiton is just auto generated code by abp-suite. ``` public virtual async Task

Abp suite may not be compatible with your old version.

try to remove suite and install again.

I am new to abp.io and abp suite so bear with me : we **did** update (via abp suite) the easycrm 2.6

So when you update Suite and don't update your solution, then the new Suite cannot find the required

If your project is v2.7.0 then use Suite v2.7.0 If you update Suite then update your solution to the

Exception message and stack trace**: * **Steps to reproduce the issue**: macos easycrm project abp suite

send your suite project create screenshot.

Hi, I haveused Abp Suite 2.7.0 to create a new solution to Demo my team.

Hi, I have integrated Telerik into the solution before. now when I try to upgrade suite to 2.8.0, I

Below is my process to create this issue: 1) Using ABP Suite 2.6.2, I generated a new solution using

You means I should update abp suite? 

if yes, you need to remove the project from Suite and add again.

,"details":null,"validationErrors":null}} abp Suite v2.6.2.0 © 2020 Copyright by Volosoft On CMD [

14:05:27 INF] ABP CLI (https://abp.io) [14:05:27 INF] Version 2.6.2 (Stable channel) Starting Suite v2.6.2.0

I am using **abp cli** and **abp suite** version 2.6.2.0.

I updated to ***ABP Suite 2.7.0.0*** today.

The project was originally created with ***ABP Suite 2.6.2***. 2.

Please Re-install ABP suite .

**ABP Suite 2.7.0.0** **node/yarn Versions** !

Update the ABP CLI: `dotnet tool update -g Volo.Abp.Cli` Update the ABP Suite: `abp suite update`

ABP suite is one option but In case, what if project solution structure has been changed.