Activities of "FrancoisLabelle"

I think it's about time to get all the same features of the Identity Management using Blazor or MVC. Blazor version still lacks a lot of features since a very long time:

• Drag and drop of Organisation units
• While editing a user, while in the "Roles" tab
  • Having roles inherited from OU assignations suffixed with (OU) and grayed out (unclickable).
  • Having roles counts in the Tab titles. E.g. Roles (2)
• While editing a user...
  • What hapenedd to the Or. units tab (7.2.3 has nothing in it ?!?!)
  • Display the list of OU assigned to the user.
  • Display to counts of Org.Units in tab title.

Capture of Mvc...

Capture of Blazor (server)

By the way, the fact that using Blazor, we can uncheck an inherited role, save, and come back to see it's still there, can also be considered as a bug.

Thanks.

Hello,

I have a similar issue... Restore of package is working... In facts, it's the "Commercial Nuget Source" feed that is "kind of broken".

I don't know if it's intended or not, but with the Nuget Package Manager inside visual studio, we cannot browse packages.

My nuget source is set to https://nuget.abp.io/[our own GUID]/v3/index.json as expected...

It's like if your nuget API endpoints are not "fully working" as expected ?!?!?

ABP suite is almost unusable to maintain an application, especialy after a while when modifications has occured in the first version of generated code. Doing a simple update, like adding a new field to an entity, has 95% odds to break the code, the tests, and needs manual file comparisons, fixes and implies a lot of error possibilites.

But, I think that if the first class generated were made using partial class and partial methods... and the code being generated marked by #region block and/or some comments marker like "/* ABPSuite generated code, do not do code change below/above */, then it will make updates possible (and easier to deal with in ABP Suite code generator).

Then, some "inteligence" could be added in the code generatior and start to "update the code", not just restarting from scratch and igoring the changes made by others...

ABP Suite is a nice tool, able to save us A LOT of time, but it misses some features to still be a great value after the initial applcation creation.

Yes, it's working again, thanks.

Hello,

I have issues trying to install ABP Suite using this dotnet command:

dotnet tool install -g Volo.Abp.Suite --add-source https://nuget.abp.io/[ourkey]/v3/index.json --version 5.3.5 --ignore-failed-sources ([ourkey] means I erased our guid it in this ticket).

I have to use this because abp suite install --version 5.3.5 fails too caused by a sources in my default nuget configuration that needs authentication (managed by VS but not on the command line),

By the way, I can install the latest version (7.0.2) without any problems, but none of the previous version (not even 6.0.0 or 7.0.0).

I still need previous versions !!!

Here are the error log:

C:\Program Files\Microsoft Visual Studio\2022\Professional>dotnet tool install -g Volo.Abp.Suite --add-source https://nuget.abp.io/[ourkey]/v3/index.json --version C:\Users\flabelle\AppData\Local\Temp\d060686e-24ca-4679-b255-310c5ff1ce11\restore.csproj : warning NU1801: Unable to lo ad the service index for source https://[cut...]v3/index.js on. C:\Users\flabelle\AppData\Local\Temp\d060686e-24ca-4679-b255-310c5ff1ce11\restore.csproj : warning NU1801: Unable to lo ad the service index for source https://p[cut...]/nuget/v3/index.js on. C:\Program Files\dotnet\sdk\7.0.103\NuGet.targets(132,5): error : Failed to download package 'volo.abp.suite.5.3.5' fro m 'https://nuget.abp.io/<ourkey>3/v3/package/volo.abp.suite/5.3.5/volo.abp.suite.5.3.5.nupkg '. [C:\Users\flabelle\AppData\Local\Temp\d060686e-24ca-4679-b255-310c5ff1ce11\restore.csproj] C:\Program Files\dotnet\sdk\7.0.103\NuGet.targets(132,5): error :** Response status code does not indicate success: 500 ( Internal Server Error**). [C:\Users\flabelle\AppData\Local\Temp\d060686e-24ca-4679-b255-310c5ff1ce11\restore.csproj] The tool package could not be restored. Tool 'volo.abp.suite' failed to install. This failure may have been caused by:

• You are attempting to install a preview release and did not use the --version option to specify the version. (Yes, I did !)
• A package by this name was found, but it was not a .NET tool. ** (It should still exists)**
• The required NuGet feed cannot be accessed, perhaps because of an Internet connection problem. (No, I can install the latest version)
• You mistyped the name of the tool. (No, the name is OK)

I need this working again ASAP.

Regards

Hello,

• ABP Framework version: v7.0
• UI type: Blazor Server
• DB provider: EF Core
• **Tiered: Yes
• Exception message and stack trace:
• Steps to reproduce the issue:"
• 1 - Create a new project using the app-pro template. DbMigrator. Run. Everything is fine.
• 2 - Use ABP Suite, add the CmsKit Pro Module. The solution will not compile due to these errors about CmsKitProAdminBlazorServerModule and the namespace Volo.CmsKit.Pro.Admin.Blazor.Server.

By the way, during the process of adding the module... there is a prompt in background (command line window) asking to scroll and choose the version of the CmsKit pro... Why I should pick the version ?!?! Is this a default behavior of NuGet ?!?!

Thanks

I did another test using --with-public-website when creating my initial project, and then CmsKit Pro was already installed with all the needed package referenced.

But, let's say I don't want or need the public web site project in my solution...but still want to use some features of the CmsKit... Let's say I just want to use the UrlShorting feature in my Blazor project... Why adding the CmsKit Pro module is not worlking if my inital project don't have the public web part ? Should it work anyway ? I think so...

Any advice are welcome, thanks.

Hello,

I added this "question" just in case someone got this issue in the future... I already found found a work around...

But, maybe ABP Team can also do something to prevent this... ?

We have a non-tiered blazor server solution deployed in Azure, using version ABP 5.2.2. Everything is working well since months...

Nothing has changed recently (no new deployment) or any parameter changes on Azure.... (Well, something has changed... not in Azure...keep reading !)

But, we recently started to have a problem. We were not able anymore to access the /identity/users page anymore (where you can manage users). And other pages were all still working correctly...

This error was being logged in the default log file, but without any more details (before or after).

Unhandled exception rendering component: '0x1F' is an invalid start of a value. LineNumber: 0 | BytePositionInLine: 0.

System.Text.Json.JsonReaderException: '0x1F' is an invalid start of a value. LineNumber: 0 | BytePositionInLine: 0.
   at System.Text.Json.ThrowHelper.ThrowJsonReaderException(Utf8JsonReader& json, ExceptionResource resource, Byte nextByte, ReadOnlySpan`1 bytes)
   at System.Text.Json.Utf8JsonReader.ConsumeValue(Byte marker)
   at System.Text.Json.Utf8JsonReader.ReadFirstToken(Byte first)
   at System.Text.Json.Utf8JsonReader.ReadSingleSegment()
   at System.Text.Json.Utf8JsonReader.Read()
   at System.Text.Json.JsonDocument.Parse(ReadOnlySpan`1 utf8JsonSpan, JsonReaderOptions readerOptions, MetadataDb& database, StackRowStack& stack)
   at System.Text.Json.JsonDocument.Parse(ReadOnlyMemory`1 utf8Json, JsonReaderOptions readerOptions, Byte[] extraRentedArrayPoolBytes, PooledByteBufferWriter extraPooledByteBufferWriter)
   at System.Text.Json.JsonDocument.Parse(ReadOnlyMemory`1 json, JsonDocumentOptions options)
   at System.Text.Json.JsonDocument.Parse(String json, JsonDocumentOptions options)
   at Volo.Abp.BlazoriseUI.Components.ObjectExtending.LookupExtensionProperty`2.GetLookupItemsAsync(String filter)
   at Volo.Abp.BlazoriseUI.Components.ObjectExtending.LookupExtensionProperty`2.SearchFilterChangedAsync(String filter)
   at Volo.Abp.BlazoriseUI.Components.ObjectExtending.LookupExtensionProperty`2.OnInitializedAsync()
   at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync()
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)

After reading this post...

https://www.byteblocks.com/Post/0x1F-is-an-invalid-start-of-a-value (as of today, their TLS certificate is expired, continue on this site only if you want... I'm not telling you to do it).

... that is basically explaining that the issue might be related to compression / "gzip"... And, the post also mentioned that the person is using Cloudfare and that Coudfare might do compression while proxying the data in transit.

Bingo ! Lucky that I'm aware of this, but we recently moved some DNS management to Cloudfare... and all our DNS entries were set to their default mode "Proxied", meaning that the user does not directly hit Microsoft Azure server but reach Cloudfare server instead... Cloudfare doing the proxying.

Then. turning off the "proxied mode" to "DNS Only" fixed the issue instantly... The /identity/users pages restarted to work.

ABP Team, you appear to also use Cloudfare... so you could maybe try to reproduce this issue... or have already experienced it ?

Maybe you are already aware of this potential issue and maybe have already fixed it ?

By the way, we also have tiered solutions (api, ids, blazor server) deployed on Azure (but using 5.3.5) that were also "proxied" by Cloudfare and we did not had this issue... We did not took any chances and we turned off the proxy feature for now... but if ABP can confirm something about it, we might want to turn it back on in the future.

Regards

Hi,

Do you mean that or that

Regards

Well... the first post https://github.com/abpframework/abp/issues/10016#issuecomment-917707186 mentioned, at the end, that there is no such "abp downgrade" command and that you don't find that this feature would be useful...

So I guess that I have my answer... and that downgrading will remain very painfull... especialy in a large solution with custom modules.

Otherwise, what about this recuring error:

[10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.aspnetcore.mvc.ui.theme.lepton/index.json with an error: 404-Not Found. Waiting 7 secs for the next try...

... repeating for all modules and several times during an update process ?

• ABP Framework version: v6.0.1 (version of ABP CLI)
• Steps to reproduce the issue:" > abp update -version 5.3.3

Is it possible to downgrade the Nuget packages of a solution ?

The documentation does not mention this... possible or impossible. Neither found a "support question" about this ?!?!?

I tried a downgrade, but I just received errors message without any detail: Unable to update package. (I woul like to know why).

E.g.

[10:38:41 WRN] Unable to update package "Volo.Abp.PermissionManagement.Application" version v5.3.4 to v5.3.3. [10:38:41 WRN] Unable to update package "Volo.Abp.PermissionManagement.Application.Contracts" version v5.3.4 to v5.3.3. [10:38:41 WRN] Unable to update package "Volo.Abp.FeatureManagement.Application" version v5.3.4 to v5.3.3. [10:38:41 WRN] Unable to update package "Volo.Abp.Caching.StackExchangeRedis" version v5.3.4 to v5.3.3. [10:38:41 WRN] Unable to update package "Volo.Abp.FeatureManagement.Application.Contracts" version v5.3.4 to v5.3.3.

Of course, I guess that when trying to do this, NuGet warns us about a package downgrade for other packages (not yet downgraded) ( NU1605 ) but this is something that I was expecting to be managed by the ABP CLI... There is certainly a way to ignore, at least temporary, these warning during the downgrade process ? I understand that we should not do this... (downgrade)... but let's say we are trying to debug something and we want to to try this downgrade... doing this manually is absolutely painful. !!!

At the same time. during an update procedure (even to upgrade to a higher version), there is a lot of these errorsthat I feel just slows down the overral process. Is this expected ? ...

[10:38:42 WRN] Unable to update package "Volo.Abp.BlobStoring.Database.Domain" version v5.3.4 to v5.3.3. [10:38:42 WRN] 1. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.identity.pro.entityframeworkcore/index.json with an error: 404-Not Found. Waiting 2 secs for the next try... [10:38:42 WRN] 1. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.identity.pro.domain/index.json with an error: 404-Not Found. Waiting 2 secs for the next try... [10:38:44 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.saas.host.application/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [10:38:44 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.saas.host.application.contracts/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [10:38:44 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.auditlogging.httpapi/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [10:38:44 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.saas.host.httpapi.client/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [10:38:44 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.account.pro.public.application/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [10:38:44 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.aspnetcore.mvc.ui.theme.lepton/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [10:38:44 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.identity.pro.domain.shared/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [10:38:44 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.identity.pro.entityframeworkcore/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [10:38:44 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.identity.pro.domain/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.saas.host.application/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.saas.host.application.contracts/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.saas.host.httpapi.client/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.account.pro.public.application/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.auditlogging.httpapi/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.identity.pro.domain.shared/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.aspnetcore.mvc.ui.theme.lepton/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.identity.pro.entityframeworkcore/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.identity.pro.domain/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [10:38:56 WRN] Unable to update package "Volo.Saas.Host.Application" version v5.3.4 to v5.3.3. [10:38:56 WRN] 1. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.auditlogging.application/index.json with an error: 404-Not Found. Waiting 2 secs for the next try... [10:38:56 WRN] Unable to update package "Volo.Abp.Identity.Pro.Domain.Shared" version v5.3.4 to v5.3.3. ...

Thanks

Hello,

Version 6.0.0 (final release) is OK... well... after a second try. I have updated CLI to 6.0.0 and Suite to 6.0.0, started it... and I got errors while trying to update packages.

2022-10-06 11:08:11.223 -04:00 [ERR] Value cannot be null. (Parameter 'source') System.ArgumentNullException: Value cannot be null. (Parameter 'source') at System.Linq.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument) at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable1 source, Func2 predicate, Boolean& found) at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable1 source, Func2 predicate) at Volo.Abp.Cli.ProjectModification.VoloNugetPackagesVersionUpdater.GetLatestVersionFromMyGet(String packageId) in D:\ci\Jenkins\workspace\abp-commercial-release

I closed everything... deleted the suite.dll in my %temp% folder (because I had issues with this previously)... started ABP Suite and proceed to update... Then, everything went well, fast, and without any update of unwanted folders...

Thanks.