Activities of "arctechnicalteamaus"

Thank you! Provided solution worked - delete all bin-obj folders, uncheck "Edit and continue" option, restart VS.

The strange thing is - if we reverted code back, just before adding our new project, everyting works fine, even with "Edit and continue" checked. Anyay.

Thanks very much for helping us!

Dear Support,

It looks like ASP.NET Zero licensing prevented us adding new project in the same solution, and we cannot Start the site without debugging under Debug mode.

Here is what we have done and noticed:

• We added a new "Framework" project into the generated solution. This project has extra extensions, library code etc. It is used by Product.Core.Shared project.
• Under Debug mode, Start without debugging shows an error screen - the site cannnot be reached.
• Works fine if using "Start debugging".
• Works fine if using Release mode, Start without debugging
• Renamed the project "Product.Framework", the same issue occurs. The "Product" is our generated code product name.
• All unit tests run fine, including additions from our own logic.

Is this caused by licesing or anything else? Can we add own extra project into the solution?

Thanks!

Dear Support,

We are trying to use Abp.Domain.Entities for our DDD development. The base Entity class defines:

public virtual TPrimaryKey Id { get; set; }

The interface IEntity<TPrimaryKey> also defines:

TPrimaryKey Id { get; set; }

In DDD work, we suppose property shouldn't allow any public setter, particularly for the Id property. We just wonder why aspnetboilerplate setup in this way. Do we miss anything? How can we change this to only allow public get?

Thanks!

We just downloaded the latest project generated ZIP file for version 7.1.0 (.net core + Angular). Noticed all file are in UNIX format (new lines are not CR/LF). Is it a mistake or on purpose?

Thanks you all for inputs. Understand there will be modification work until the Abp vNext comes out. Would the following approach work?

1. Use ASP.NET Zero application as the Access API, and the front-end (Angular). This Access API manages authentication, authorization.
2. Use ASP.NET Zero application API part (no need for front end) as a base, for other API - our own business logic, but we need to re-route authentication, authorization part to use the above Access API.

Can you see any major problems? allowed by your licensing terms?

Regards, Richard

Dear support,

We have an existing application, and just purchased ASP.NET Zero. Our current application uses a Microservices approach. Front end is Angular, calling an API Gateway for all API. Behind the API gateway, there are 4 API services, such as authentication API, report API, main business logic API etc. There are multiple PostgreSQL databases too.

I know you have a next version ABP under development, with focus on Microservices. But for the current version of ASP.NET Zero, can you recommend how we can adopt the Microservices approach? Is there a recommended way, so it is easier to migrate to your next version in the future?

Thanks! Richard