Activities of "cellero"

** update I compared a new solution and the UiFramework is 7 whereas my existing project had 4

Is 7 the new 4!?

Ok, but I created it as a WebApp.

I'm facing the same issue

Its empty:

Ok thank you.

I missed this piece:

It is working now.

hi karl.ettinger

Can you rebuild and publish the website?

Sorry for your production website. Please get in touch with us(info@abp.io). We will do something.

Hi Maliming, I would like to understand this as well. I also had a site go down.
I am concern that a fully deployed system has dependencies on ABP.

Can you please advise what is being done to prevent this.

Thank you.

How did it suddenly stop working? We had a functional 9.1.0 build that was working without errors.

This is a serious / important question. I had a fully deployed system that stopped working due to this issue.
The system has a requirement to have high availability.

My customer will not accept this type of architecture whereby the site availability is dependent on a third party.

@ABP - Do you agree? Do you think a chance is required here?

Hi everyone,

We sincerely apologize for the issue caused by the recent release with a 3rd party component. The affected versions are 9.0.7 and 9.1.0, other versions don't have any issue. We understand how frustrating it is, especially when it affects live systems. The ABP project, like other software solutions, includes many 3rd party components, and sometimes there may be problems with them. We contacted our 3rd party vendor and completely fixed the case.

The issue is now resolved, and here's the quick fix:

1. Run this command on your development computer to clear your local NuGet cache:
   dotnet nuget locals all --clear

2. Uninstall and install ABP Suite again:
   abp suite remove
abp suite install

3. Rebuild your ABP solution and publish it again to your live environment

Thank you for your patience, and we truly appreciate the feedback. We're taking extra measures to prevent this in future releases.

– ABP Team

I'm sorry, that is not an explanation of what went wrong, and gives us no reassurance that it won't happen again.

We have customers that cannot tolerate an outage like this, and saying "someone else will fix it in the next day" is NOT an acceptable answer. Being may time zones away that means we are effectively shutting down their business for at least a day.

We put a LOT of effort into creating an offline build so that we are not affected by a temporary outage of any NuGet servers, but this problem stopped logins in code that was already functional and deployed. That means that 1 of 2 things happened, both of which are unacceptable:

1. A component in our compiled code is reaching out to a server live to determine if it is allowed to run
2. A license code embedded in our dependencies has an expiration date that we do not know about

We need to answer our organizations with a specific cause for this outage, or we will be forced to abandon ABP entirely (which we do not want to do).

Well said. I 100% agree. I am watching this space for ABP to acknowledge this is an architectural flaw and needs to be rectified.