- ABP Framework version: v4.4.3
- UI type: MVC
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): no
- Exception message and stack trace:
- AbpException: Could not find the bundle file '/Themes/Lepton/Global/Styles/lepton2.css' for the bundle 'Lepton.Global'!
Volo.Abp.AspNetCore.Mvc.UI.Bundling.TagHelpers.AbpTagHelperResourceService.ProcessAsync(ViewContext viewContext, TagHelperContext context, TagHelperOutput output, List<BundleTagHelperItem> bundleItems, string bundleName) Volo.Abp.AspNetCore.Mvc.UI.Bundling.TagHelpers.AbpBundleTagHelperService<TTagHelper, TService>.ProcessAsync(TagHelperContext context, TagHelperOutput output) Microsoft.AspNetCore.Razor.Runtime.TagHelpers.TagHelperRunner.<RunAsync>g__Awaited|0_0(Task task, TagHelperExecutionContext executionContext, int i, int count) AspNetCore.Themes_Lepton_Layouts_Account_Default+<>c__DisplayClass32_0+<<ExecuteAsync>b__0>d.MoveNext() in Default.cshtml + <abp-style-bundle name="@LeptonThemeBundles.Styles.Global" /> Microsoft.AspNetCore.Razor.Runtime.TagHelpers.TagHelperExecutionContext.SetOutputContentAsync() AspNetCore.Themes_Lepton_Layouts_Account_Default.ExecuteAsync() in Default.cshtml + <html lang="@CultureInfo.CurrentCulture.Name" dir="@langDir"> Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderPageCoreAsync(IRazorPage page, ViewContext context) Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderPageAsync(IRazorPage page, ViewContext context, bool invokeViewStarts) Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderLayoutAsync(ViewContext context, ViewBufferTextWriter bodyWriter) Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderAsync(ViewContext context) Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync(ViewContext viewContext, string contentType, Nullable<int> statusCode) Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync(ViewContext viewContext, string contentType, Nullable<int> statusCode) Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeResultAsync>g__Logged|21_0(ResourceInvoker invoker, IActionResult result) Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResultFilterAsync>g__Awaited|29_0<TFilter, TFilterAsync>(ResourceInvoker invoker, Task lastTask, State next, Scope scope, object state, bool isCompleted) Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResultExecutedContextSealed context) Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.ResultNext<TFilter, TFilterAsync>(ref State next, ref Scope scope, ref object state, ref bool isCompleted) Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeResultFilters>g__Awaited|27_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, object state, bool isCompleted) Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|24_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, object state, bool isCompleted) Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context) Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(ref State next, ref Scope scope, ref object state, ref bool isCompleted) Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|19_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, object state, bool isCompleted) Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Logged|17_1(ResourceInvoker invoker) Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger) Volo.Abp.AspNetCore.Serilog.AbpSerilogMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+<>c__DisplayClass6_1+<<UseMiddlewareInterface>b__1>d.MoveNext() Volo.Abp.AspNetCore.Auditing.AbpAuditingMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Volo.Abp.AspNetCore.Auditing.AbpAuditingMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+<>c__DisplayClass6_1+<<UseMiddlewareInterface>b__1>d.MoveNext() Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext) Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider) Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context) IdentityServer4.Hosting.IdentityServerMiddleware.Invoke(HttpContext context, IEndpointRouter router, IUserSession session, IEventService events, IBackChannelLogoutService backChannelLogoutService) IdentityServer4.Hosting.MutualTlsEndpointMiddleware.Invoke(HttpContext context, IAuthenticationSchemeProvider schemes) Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context) IdentityServer4.Hosting.BaseUrlMiddleware.Invoke(HttpContext context) Volo.Abp.AspNetCore.Uow.AbpUnitOfWorkMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+<>c__DisplayClass6_1+<<UseMiddlewareInterface>b__1>d.MoveNext() Volo.Abp.AspNetCore.ExceptionHandling.AbpExceptionHandlingMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Volo.Abp.AspNetCore.ExceptionHandling.AbpExceptionHandlingMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+<>c__DisplayClass6_1+<<UseMiddlewareInterface>b__1>d.MoveNext() Microsoft.AspNetCore.Builder.ApplicationBuilderAbpJwtTokenMiddlewareExtension+<>c__DisplayClass0_0+<<UseJwtTokenMiddleware>b__0>d.MoveNext() Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context) Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context) Microsoft.AspNetCore.RequestLocalization.AbpRequestLocalizationMiddleware.InvokeAsync(HttpContext context, RequestDelegate next) Microsoft.AspNetCore.Builder.UseMiddlewareExtensions+<>c__DisplayClass6_1+<<UseMiddlewareInterface>b__1>d.MoveNext() Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)
- Steps to reproduce the issue:"
- Upgraded to ABP Framework 4.4.3 and launched the app
I saw this existing issue logged and can confirm that the file Directory.Build.props is in place: https://support.abp.io/QA/Questions/1480/Error-AbpException-Could-not-find-the-bundle-file-after-adding-source-code-of-Lepton-Theme-in-my-project
9 Answer(s)
-
0
Just an additional note. I do have the source code for Lepton Theme added to my solution via the ABP Suite Modules. If it is going to be easier to remove it from my solution I am happy to do that
-
0
HI,
I actually don't know why this problem occurs, but if you can share a project to reproduce it, I can help you solve the problem, shiwei.liang@volosoft.com
I do have the source code for Lepton Theme added to my solution via the ABP Suite Modules. If it is going to be easier to remove it from my solution I am happy to do that
May be you can try it.
-
0
HI,
I actually don't know why this problem occurs, but if you can share a project to reproduce it, I can help you solve the problem, shiwei.liang@volosoft.com
I do have the source code for Lepton Theme added to my solution via the ABP Suite Modules. If it is going to be easier to remove it from my solution I am happy to do that
May be you can try it.
Thank you I have shared on GitHub. How do we go about removing the adding of the LeptonThem code from the solution?
-
0
Thank you I have shared on GitHub
I will check it.
How do we go about removing the adding of the LeptonThem code from the solution?
You just need replace the LeptonTheme local project reference to Nuget Packages.
-
0
-
0
-
0
-
0
Hi. I had to remove the source code for the Account as well. This seems to have worked in the development environment. However when publishing to the Azure Web App the following build errors occur below. To confirm the code builds and runs properly in the developement environment.
##[error]modules\Volo.Account.Pro\test\Volo.Abp.Account.Pro.Application.Tests\Volo\Abp\Account\FakeBlobProvider.cs(19,47): Error CS0246: The type or namespace name 'BlobProviderExistsArgs' could not be found (are you missing a using directive or an assembly reference?) D:\a\1\s\modules\Volo.Account.Pro\test\Volo.Abp.Account.Pro.Application.Tests\Volo\Abp\Account\FakeBlobProvider.cs(19,47): error CS0246: The type or namespace name 'BlobProviderExistsArgs' could not be found (are you missing a using directive or an assembly reference?) [D:\a\1\s\modules\Volo.Account.Pro\test\Volo.Abp.Account.Pro.Application.Tests\Volo.Abp.Account.Pro.Application.Tests.csproj] ##[error]modules\Volo.Account.Pro\test\Volo.Abp.Account.Pro.Application.Tests\Volo\Abp\Account\FakeBlobProvider.cs(24,46): Error CS0246: The type or namespace name 'BlobProviderGetArgs' could not be found (are you missing a using directive or an assembly reference?) D:\a\1\s\modules\Volo.Account.Pro\test\Volo.Abp.Account.Pro.Application.Tests\Volo\Abp\Account\FakeBlobProvider.cs(24,46): error CS0246: The type or namespace name 'BlobProviderGetArgs' could not be found (are you missing a using directive or an assembly reference?) [D:\a\1\s\modules\Volo.Account.Pro\test\Volo.Abp.Account.Pro.Application.Tests\Volo.Abp.Account.Pro.Application.Tests.csproj] ##[error]modules\Volo.Account.Pro\test\Volo.Abp.Account.Pro.Application.Tests\Volo\Abp\Account\FakeBlobProvider.cs(29,52): Error CS0246: The type or namespace name 'BlobProviderGetArgs' could not be found (are you missing a using directive or an assembly reference?) D:\a\1\s\modules\Volo.Account.Pro\test\Volo.Abp.Account.Pro.Application.Tests\Volo\Abp\Account\FakeBlobProvider.cs(29,52): error CS0246: The type or namespace name 'BlobProviderGetArgs' could not be found (are you missing a using directive or an assembly reference?) [D:\a\1\s\modules\Volo.Account.Pro\test\Volo.Abp.Account.Pro.Application.Tests\Volo.Abp.Account.Pro.Application.Tests.csproj] ##[error]modules\Volo.Account.Pro\test\Volo.Abp.Account.Pro.Application.Tests\Volo\Abp\Account\AccountEmailer_Tests.cs(17,26): Error CS0246: The type or namespace name 'IAccountEmailer' could not be found (are you missing a using directive or an assembly reference?) D:\a\1\s\modules\Volo.Account.Pro\test\Volo.Abp.Account.Pro.Application.Tests\Volo\Abp\Account\AccountEmailer_Tests.cs(17,26): error CS0246: The type or namespace name 'IAccountEmailer' could not be found (are you missing a using directive or an assembly reference?) [D:\a\1\s\modules\Volo.Account.Pro\test\Volo.Abp.Account.Pro.Application.Tests\Volo.Abp.Account.Pro.Application.Tests.csproj] ##[error]modules\Volo.Account.Pro\test\Volo.Abp.Account.Pro.Application.Tests\Volo\Abp\Account\AccountEmailer_Tests.cs(18,17): Error CS0246: The type or namespace name 'IEmailSender' could not be found (are you missing a using directive or an assembly reference?) D:\a\1\s\modules\Volo.Account.Pro\test\Volo.Abp.Account.Pro.Application.Tests\Volo\Abp\Account\AccountEmailer_Tests.cs(18,17): error CS0246: The type or namespace name 'IEmailSender' could not be found (are you missing a using directive or an assembly reference?) [D:\a\1\s\modules\Volo.Account.Pro\test\Volo.Abp.Account.Pro.Application.Tests\Volo.Abp.Account.Pro.Application.Tests.csproj] ##[error]modules\Volo.Account.Pro\test\Volo.Abp.Account.Pro.Application.Tests\Volo\Abp\Account\AccountEmailer_Tests.cs(21,43): Error CS0246: The type or namespace name 'AccountResource' could not be found (are you missing a using directive or an assembly reference?) D:\a\1\s\modules\Volo.Account.Pro\test\Volo.Abp.Account.Pro.Application.Tests\Volo\Abp\Account\AccountEmailer_Tests.cs(21,43): error CS0246: The type or namespace name 'AccountResource' could not be found (are you missing a using directive or an assembly reference?) [D:\a\1\s\modules\Volo.Account.Pro\test\Volo.Abp.Account.Pro.Application.Tests\Volo.Abp.Account.Pro.Application.Tests.csproj] CompilerServer: server - server processed compilation - e3d1d1a4-c159-4e2c-a72c-606cbdfa0055
-
0
Ok resolved now. Even though the modules folder was deleted from Visual Studio they still needed to be deleted from the directory structure in file explorer. Rebuilt and published fine. App now up and running.
Thank you for your support.