أنشطة "kbowma"

• ABP Framework version: v5.1.2
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): Microservice Template (Blazor WASM)
• Exception message and stack trace:
• Steps to reproduce the issue:"

I have read all the threads (and posted my own) on redirecting to login (or separate landing page) when the application starts but there does not seem to be a straight forward answer that does not have the issue of the index page first showing then redirecting to login. So, my question is... has anyone been able to find a solution for having the Blazor WASM application go directly to a login page (or landing page) without having the index page first flash up as it is redirecting?

When upgrading a project from 5.0.0 to 5.0.1 in ABP Suite UI, it deletes all files in the target directory. Also deletes .suite folder if entities have been defined.

Also, a minor detail, the version of suite is still showing 5.0.0.

• ABP Framework version: v5.0.1
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes (microservice)
• Exception message and stack trace:
• Steps to reproduce the issue: Upgrade to ABP Suite 5.0.1 from 5.0.0. Start ABP Suite UI and select the version from one of the microservice projects in the list. Select Upgrade all ABP packages from the dropdown. Operation completes successfully. Note that I upgraded two projects, the first having entities defined and the second having no entities defined. All files in the output directory are deleted. With the project that had entities defined, the .suite folder has also been deleted.

When using ABP Suite Load Entity from Database, it seems that it does not support schema names as part of the table name. Would you confirm that schemas are not supported and indicate if/when they will be supported? Our database is defined with [schema name].[table name].

If you're creating a bug/problem report, please include followings:

• ABP Framework version: v5.0.0
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes (microservice)
• Exception message and stack trace: Cannot retrieve tables! Cannot convert table to entity! Object not set to instance of an object
• Steps to reproduce the issue:" Add connection string, click check connection. (all okay) then click connect. You receive the error dialog.

Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.

• ABP Framework version: v4.3.0
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace:
• Steps to reproduce the issue:

When generating an entity for a module in ABP suite, the UI is not generated even though "Create user interface" is selected.

• ABP Framework version: v4.2.2
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace:
• Steps to reproduce the issue:

I have a client side Blazor application where I am trying to nest layouts per the below diagram. I have an Abp.io module that contains a "TestLayout" component that inherits from LayoutComponentBase. It is rendered from a menu item on the main application sidebar. In the TestLayout component I have a Telerik Drawer component that uses NavigationManager to render a separate page (Page1/2) into its content @Body. Each page component defines a @layout of TestLayout. Now, the initial state loads fine and when I select the TestLayout from the main sidebar menu, it will load the TestLayout correctly. When I select Page 1 from the Telerik Drawer the Page 1 is rendered in the Content @Body correctly, but the TestLayout component replaces all application components so it is the only component rendered on the page (I loose the Apb.io Sidebar and Toolbar). I am assuming this is because I have not defined a @layout in the TestLayout component to render in the @body of the main application. Because I am in a module I don't think I have access to the main layouts  (MainLayout?). How do I ensure my TestLayout component in module A will render in the main applications @body when I have nested layouts?