Activities of "alper"

@pvaz can you share the GitHub link of the comment that solves in RC-4.1

good! so update it to 3.3.2 I'm closing the issue. reopen if it continues... happy coding.

good to hear that. closing the issue

robb@designitcorp.ca it doesn't matter where the solution is located. the entites must be inside the root folder of the solution (in .suite/entities folder)

can you send us the project? info@abp.io

@pvaz if you upgraded from 3X to 4X see this post https://docs.abp.io/en/abp/4.0/Migration-Guides/Abp-4_0 also check out https://github.com/abpframework/abp/issues/5950#issue-729718680

robb@designitcorp.ca check out https://support.abp.io/QA/Questions/625/How-to-include-Suite-entities-in-my-source-control-system#answer-1287c0f9-c787-9953-f091-39f9374847bc

This feature is implemented in v4.0.0 RC.5 and the release of RC5 is 2020-12-04. Starting from v4.0, your entities will be located in the .suite folder in your solution's root directory. On the other hand to keep the same behaviour for the old projects, it still saves it in the existing directory => %UserProfile%\.abp\suite\solutions\{solution-id}\entities\

if you want your Suite entities to be included in your Git system, follow the steps:

• create a folder named .suite in your root directory.
• move all your entites (*.json) from %UserProfile%\.abp\suite\solutions\{solution-id}\entities\ folder to the new folder .suite/entities
• delete entities folder (mandatory) => %UserProfile%\.abp\suite\solutions\{solution-id}\entities

@developer1 "Cannot read the template" issue is related with version conflicts with the solution and Suite. and I see some of them has been resolved in v4.0.0-rc5

robb@designitcorp.ca it's already fixed in the newer versions. the simple solution is remove - add again the same solution.