Activities of "sean.alford"
@Alper,
The Ticket entity does have an Id (Guid). It inherits from FullAuditedAggregateRoot. I guess I could use an int/long for the Id and display the Id on the UI as the Ticket #. However, the ticket numbers would not be sequancial across tenants so that wouldn't work.
To be honest I'm not following your proposed solution. Are you suggesting that I create a new entity/repo (SequentialNumber) just to store a Ticket Number? We do not need SequenceName, just a int/long. This seems like a lot of extra effort to provide this Ticket Number requirement. Especially since the RDBMS already provides this functionalitly.
Questions How are you guys storing the Question #? This question is #150. Where is that value storted? Is it the Question Id, a property of Question, or is it a navigation link that is stored in seperate table?
I need to create a Navigation Link to an application/tenant user. Where is the AppUserDto located?
@Alper, I cannot find the AppUserDto in the applications contrarcts project. The AppUsers model is in the domian project where you'd expect it to be.
@Alper,
I did not create the AppUser entity. It is definded within the ABP.io app-pro template.
I searched for the AppUserDto within the solution, but nothing was found. As you can see it is not defined in the Application.Contracts where you'd expect it to be.
ABP Suite: 2.7.0.0
FYI: When you choose long for your PK type, there are several places within the project templates that are not getting substitude properly.
@alper I ran into a new problem this morning when I tried to start ABP.io Suite. I see @roop.yekollu@atlasair.com is have a similar problem. So I followed your instructions to them and manually deleted %UserProfile%\.dotnet\tools\.store\volo.abp.suite. However, as you can see the install is failing.
NOTE: I am logged into ABP via CLI in an Administrative Command Prompt
@alper, it looks like my virus protection is removing Volo.Abp.Suite.dll
ABP.io Suite installed after I manually deleted it, and Update Restart Windows.
However, if failed to start after the Windows Update Restart
Norton Screen Shots
Cosmetic/Translation
This message should probably be read something like the following.
"The 'Acme.HelpDesk' solution needs to be built prior to code generation. Do you wish to continue?"
"The 'Acme.HelpDesk' solution must be built prior to code generation. Do you wish to continue?"
@alper, I think I found another issue this afternoon.
ABP Suite - Created
ABP Suite - Should Create
According to the comments here in the Acme.HelpDesk.Domain.Users.AppUser.cs, I should be able to extend AppUser by adding new properties. (i.e. public virtual Guid OrganizationId { get; set; })
Acme.HelpDesk.Domain.Users.AppUser.cs
Next, I would need to configure the mapping for the properties here: HelpDeskDbContext.OnModelCreating
Then I would need to update HelpDeskEfCoreEntityExtensionMappings
Finally, I created the migration; however, as you can see the FK mapping did not get created as expected.
How do I correct this?
Trouble updating ABP Suite 2.8.0
