Activities of "improwise"

Please stop closing this as there is still no Docker support available. Thanks.

Hi,

I'm a little busy with other high-priority work, possibly within the next two studio releases

What does that mean in terms of weeks/months?

We've been holding off on starting this new project mainly due to both Docker support and React Native support missing in ABP since a few months back.

This problem is not new but it is still there in ABP 9 so...

It seems like if you are running new ABP CLI with a Windows user name containing a space like "NAME NAME" it will normally work. However, if you add "--old" parameter it will no longer work but instead give error message

With --old: M:\Projects\ABP\src>abp new Acme.BookStore3 --old [15:14:51 ERR] 'C:\Users\NAME' is not recognized as an internal or external command, [15:14:51 ERR] operable program or batch file.

Without --old: M:\Projects\ABP\src>abp new Acme.BookStore3 [15:15:18 INF] You are running the second generation of the ABP CLI. If you're interested in the legacy CLI, see https://abp.io/new-cli [15:15:18 INF] Creating your solution...

I know Windows in general has some problems with spaces in usernames, but sometimes you might not have an option but to have one, so is there a way to make it work besides uninstalling new CLI and installing old one (which does seem to work even though --old does not work)?

I reopened the question

From the other thread, what is the current status on reimplementing Docker support in ABP Commercial? Do we have a timeline?

Hi, I am trying to create a new blazor maui hybrid project with abpstudio v9 and get error at the bundle step. After many hours of digging this is what I concluded, it is an issue with the Volo.Abp.Account.Pro.Public.MauiBlazor package. Please see log from dotnet restore:
Unable to find package Volo.Abp.Account.Pro.Public.MauiBlazor. No packages exist with this id in source(s): nuget.abp.io, nuget.org. PackageSourceMapping is enabled, the following source(s) were not considered: C:\Program Files\dotnet\library-packs, Microsoft Visual Studio Offline Packages.

There seem to be some nuget issues currently based on this and other threads.

Hello, we have not made any change that would affect here. My question is whether you have customized any part that might suppress here since I cannot produce the same problem on my side.

No customization and the bug has probably been there for quite a while I would guess but does only seem to show at exactly 1200 px (at least when we have tried it).

https://abp.io/support/questions/8082/What-is-the-support-for-Docker-in-ABP-Commercial-today

hi

Can you create a new question for this? We will refund your question ticket.

Let's use the current question only to track the translation problem.

Thanks.

Added it to the genral ABP 9 bugs and issues as well as an explanation why it failed (even though you would probably need to look into this for when you upgrade).

This seems related to the topic at hand here.

Just upgraded a solution a few months old från 8.3.0 to 8.3.1 using ABP Suite which updated from

<PackageReference Include="Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX" Version="3.3.0" />

to

<PackageReference Include="Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX" Version="4.0.3" />

which makes the solution impossible to build with

The type or namespace name 'LeptonX' does not exist in the namespace 'Volo.Abp.AspNetCore.Mvc.UI.Theme' (are you missing an assembly reference?)

Downgrading to 3.3.0 makes it possible to build and run again.

Edit:

Seems you can upgrade to 3.3.1 but anything above that seems to break.

Edit 2:

Seems like something is broken in the final ABP 8 versions, but when we upgraded .NET to 9 and then all other packages to latest version, it seem to work.

Just tried this using latest ABP and Blazor Server template and problem seem to remain. Just like before, this only seem to happen when window is exactly 1200 px wide.