We will probably release a new version this week with this problem fixed.
Hello, thank you for the information you provided. We can reproduce the problems you mentioned, so I have created 2 separate internal issues related to your problems. We will solve these problems as soon as possible and release a new version of ABP Studio. Thank you for your patience and understanding.
Closing the issue. If you have any other problems with ABP Studio, please let us know here.
One other bug I noticed is that when I ran "abp update" on my solution, it also blindly updated the Volo.Abp.Studio.Client.AspNetCore package to version 8.1.3 - a version that does not exist :) I had to manually change that to 0.6.7.
Thank you very much for reporting the bugs. This issue will be resolved with this PR.
Hi,
I updated to 0.6.7 and now I can't open my solution anymore:
The log says:
2024-06-12 19:43:39.906 +02:00 [ERR] Sequence contains no matching element System.InvalidOperationException: Sequence contains no matching element at System.Linq.ThrowHelper.ThrowNoMatchException() at System.Linq.Enumerable.Single[TSource](IEnumerable`1 source, Func`2 predicate) at Volo.Abp.Studio.UI.Solutions.Items.SolutionUIModel.GetAvailableModuleTemplates() at Volo.Abp.Studio.UI.ViewModels.SolutionExplorer.Items.SolutionRootItemViewModel..ctor(SolutionUIModel model) at Volo.Abp.Studio.UI.ViewModels.SolutionExplorer.SolutionExplorerViewModel.Y73CsTB7mq() at ReactiveUI.ReactiveCommand.<>c__DisplayClass0_0.<Create>b__1(IObserver`1 observer) in /_/src/ReactiveUI/ReactiveCommand/ReactiveCommand.cs:line 90 at System.Reactive.Linq.QueryLanguage.CreateWithDisposableObservable`1.SubscribeCore(IObserver`1 observer) at System.Reactive.ObservableBase`1.Subscribe(IObserver`1 observer)
Hello, you can follow the steps below to solve your problem:
MyProjectName.abpsln
file. It is usually in the same directory as the *.sln
file.-pro
from the template element in the third line."template": "app-pro",
"template": "app",
Hello, thank you for your detailed information.
Currently the package Volo.Abp.Studio.Extensions.StandardSolutionTemplates
is not found in the your NuGet cache, somehow ABP Studio is not able to download this package. To download this package manually, execute the command below in CLI:
nuget install Volo.Abp.Studio.Extensions.StandardSolutionTemplates -version 0.6.6 -source https://nuget.abp.io/[YOUR_API_KEY]/v3/index.json
replace
[YOUR_API_KEY]
with yours (it's in your NuGet.config file)
Then move the downloaded folder into the folder with the packages in your NuGet cache. If everything was done correctly, the problem should be fixed when you open ABP Studio again.
I am trying to initialise an existing solution that loads fine in visual studio and is Blazor / Microservices based.
If I initialise each solution or microservice solution they work fine however if I try to initialise the main solution which has all projects into a single solution with 302 projects I get the following error.
I am running on Windows 11
Logs
2024-04-24 22:47:37.921 +10:00 [WRN] Exception of type 'Volo.Abp.Studio.AbpStudioException' was thrown. Volo.Abp.Studio.AbpStudioException: Exception of type 'Volo.Abp.Studio.AbpStudioException' was thrown. at Volo.Abp.Studio.Modules.ModuleManager.CreateFolderAsync(String modulePath, String folder) at Volo.Abp.Studio.Initializer.ModuleInitializer.Dj4RL1f3Wr(String , String ) at Volo.Abp.Studio.Initializer.ModuleInitializer.UtsR2fpR9p(String , Boolean ) at Volo.Abp.Studio.Initializer.ModuleInitializer.InitializeAsync(String modulePath, Boolean skipExisting) at Volo.Abp.Studio.Initializer.SolutionInitializer.InitializeAsync(String directoryPath, String solutionName) at Volo.Abp.Studio.UI.Commands.InitSolutionCommandFactory.jgiB46XYTk() 2024-04-24 22:47:37.921 +10:00 [WRN] Code:AbpStudio:InvalidFolderName 2024-04-24 22:47:37.921 +10:00 [WRN] Details: 2024-04-24 22:47:37.922 +10:00 [WRN] ---------- Exception Data ---------- Name = ../../services/identity/src
Thank you for the report, I am creating an internal issue about this.
Hello, thank you for reporting the issue to us. We are working on the problem but it is very difficult to say when it will be fixed. However, as a workaround, you can run ABP Studio with the following command with admin privilege and try again.
sudo open /Applications/ABP\ Studio.app
Feel free to report if the workaround worked :)
You can send it to berkan.sasmaz@volosoft.com address.
1.) When trying to select "ABP Suite" from the top right menu, whole application crashes and i have to force close it.
I am creating an issue for the problem related to Suite.
2.) I get an error when trying to create a new solution. "An internal error occurred during your request!"
Can you send me the log records of the ABP Studio?
Note: You can find the log file in ~/.abp/studio/ui/logs
path.
Update with 0.6.6 : same issue
Can you provide me with the following information so that I can reproduce the problem?
- Is there an
abpc
executable file in/Applications/ABP Studio.app/Contents/MacOS
folder?- Is there a symlink to
abpc
in/usr/local/bin
folder?- If the symlink is present, can you send me the full output of the terminal that opens when you double-click?
Hi, this is on windows. I now added abp folder to the env variables path (eg
C:\Program Files\Volosoft\ABP Studio
, and it seems to work, although every command is getting this error'System.TypeInitializationException: The type initializer for 'Volo.Abp.Studio.Extensions.ExtensionConsts' threw an exception. ---> System.ArgumentNullException: Value cannot be null. (Parameter 'path1') at System.ArgumentNullException.Throw(String paramName) at System.IO.Path.Combine(String path1, String path2) at Volo.Abp.Studio.Extensions.ExtensionConsts.Iq2FRp3PHuxHdPuuR4ug(Object, Object) at Volo.Abp.Studio.Extensions.ExtensionConsts..cctor() --- End of inner exception stack trace --- at Volo.Abp.Studio.Extensions.StudioExtensionLoader.GetExtensions() at Volo.Abp.Studio.Extensions.StudioAbpApplicationCreationOptionsExtensions.LoadAbpStudioExtensions(AbpApplicationCreationOptions options, StudioExtensionApplicationType type) at Volo.Abp.Studio.Cli.Program.<>c.<Main>b__0_2(AbpApplicationCreationOptions options)'
This problem will be solved with the new version, thanks for the report 🙏