Update the ABP CLI:
dotnet tool update -g Volo.Abp.Cli
Update the ABP Suite:
abp suite update
- Release notes: https://docs.abp.io/en/commercial/latest/release-notes
52 Answer(s)
-
0
Are there release notes somewhere?
-
0
@AndrewT
https://blog.abp.io/abp/ABP-Framework-v2_7_0-Has-Been-Released
https://github.com/abpframework/abp/releases/tag/2.7.0
-
0
-
0
Can't access the url http://127.0.0.1:8988/Docs/Admin/Projects after publish.
Below is the log message.
[16:16:16 INF] Request starting HTTP/1.1 GET http://127.0.0.1:8988/Docs/Admin/Projects
[16:16:17 ERR] Connection id "0HLVJU4I80GIM", Request id "0HLVJU4I80GIM:00000002": An unhandled exception was thrown by the application. Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation.CompilationFailedException: One or more compilation failures occurred: /Pages/Docs/Admin/Projects/Index.cshtml(33,28): error CS1705: 标识为“Volo.Abp.Authorization, Version=2.7.0.0, Culture=neutral, PublicKeyToken=null”的程序集“Volo.Abp.Authorization”所使用的“Microsoft.AspNetCore.Authorization, Version=3.1.2.0, Culture=neutral, PublicKeyToken=adb9793829ddae60”版本高于所引用的标识为“Microsoft.AspNetCore.Authorization, Version=3.1.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60”的程序集“Microsoft.AspNetCore.Authorization” /Pages/Docs/Admin/Projects/Index.cshtml(42,28): error CS1705: 标识为“Volo.Abp.Authorization, Version=2.7.0.0, Culture=neutral, PublicKeyToken=null”的程序集“Volo.Abp.Authorization”所使用的“Microsoft.AspNetCore.Authorization, Version=3.1.2.0, Culture=neutral, PublicKeyToken=adb9793829ddae60”版本高于所引用的标识为“Microsoft.AspNetCore.Authorization, Version=3.1.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60”的程序集“Microsoft.AspNetCore.Authorization” at Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation.RuntimeViewCompiler.CompileAndEmit(RazorCodeDocument codeDocument, String generatedCode) at Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation.RuntimeViewCompiler.CompileAndEmit(String relativePath) at Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation.RuntimeViewCompiler.OnCacheMiss(String normalizedPath) --- End of stack trace from previous location where exception was thrown --- at Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.DefaultPageLoader.LoadAsyncCore(PageActionDescriptor actionDescriptor, EndpointMetadataCollection endpointMetadata) at Microsoft.AspNetCore.Mvc.RazorPages.Infrastructure.PageLoaderMatcherPolicy.ApplyAsyncAwaited(CandidateSet candidates, Task1 actionDescriptorTask, Int32 index) at Microsoft.AspNetCore.Routing.Matching.DfaMatcher.SelectEndpointWithPoliciesAsync(HttpContext httpContext, IEndpointSelectorPolicy[] policies, CandidateSet candidateSet) at Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware.<Invoke>g__AwaitMatch|8_1(EndpointRoutingMiddleware middleware, HttpContext httpContext, Task matchTask) at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication
1 application) [16:16:17 INF] Request finished in 618.5964ms 500 -
0
@andrew the release notes for the commercial side will be available in the next week, we'll announce it. When it's ready, it will be published in the document website https://docs.abp.io/en/commercial/latest
-
0
@alpers - Thankyou, let me know which tree it is under or create a new "Release Notes" category?
-
0
@690486439 yes you have an Enterprise License, but this is a bug in Suite. It's has been addressed and fixed. You'll see the "Add to project" button in the next version.
-
0
@zony i think it's related with the Docs module on the free side so can you file an issue to https://github.com/abpframework/abp/issues
-
0
@AndrewT here's the release notes => https://docs.abp.io/en/commercial/latest/release-notes
-
0
@Alper - Thankyou! Can you tell us about progress on Blazor templates?
-
0
@AndrewT, it's in the roadmap but not in high priority. Sorry, I can't tell a deadline.
-
0
Hello,
Just want to bring your attetion to a small cosmetic issue with the tenant listing screen. It seems the table column headers are not aligning with the table column rows. Furthermore, the height of the table headers when viewed from a mobile device are wrong. Please refer to the attached images.
-
0
-
0
@roop.yekollu, can you run
abp suite remove
then
abp suite install
-
0
@ninomartini this must be fixed in the latest version. tomorrow there'll be 2.7.1 for NPM packages. then you can update it or wait for the v2.8.0
-
0
-
0
-
0
I think your app is corrupted. try deleting this directory =>
%UserProfile%\.dotnet\tools\.store\volo.abp.suite
then install again -
1
hi @sean.alford , thanks for reporting long primary key issue. Created an issue for that.
-
0
-
0
@alper I ran into a new problem this morning when I tried to start ABP.io Suite. I see @roop.yekollu@atlasair.com is have a similar problem. So I followed your instructions to them and manually deleted
%UserProfile%\.dotnet\tools\.store\volo.abp.suite
. However, as you can see the install is failing.NOTE: I am logged into ABP via CLI in an Administrative Command Prompt
-
0
-
0
That's definately a false alarm! Virus programs makes a heroistic check... A heuristic check is a method that lets a computer program "guess" about unknown stuff. The Suite DLL creates a web hosting, makes requests, accesses directories so they mark it as potentially risky. But it has nothing to do with virus. As you see from the Norton report, it says Heuristic Virus, which means the application follows a bunch of rules about what makes something look like a virus and when it sees a program that does similar things, it gets flagged as questionable.
Here's the virus total score: 2 / 72 https://www.virustotal.com/gui/file/0911c25aaee672cc24e95654cd3d96c209cc1a01dce89c04cfff5cdd48ffecbc/detection
You can ignore this and exclude Volo.Abp.Suite.dll from your antivirus.
-
0
Dynamic Form Problem Caused by Ivy in Angular UI
Hello,
We have noticed that, due to this open issue on Angular, the
DisabledDirective
breaks all dynamic forms in v2.7 of the Angular UI, when Ivy is enabled.We have implemented one of the workarounds suggested in the thread of that issue and released v2.7.2 for the commercial-ui package which fixes the problem.
If you observe anything similar, please remove yarn.lock (or package-lock.json) in your project and reinstall npm packages.
Sorry for the inconvenience.
-
0