Activities of "joe@tronactive.com"

Yes that is correct. We are using Blazor Server version.

How do I update those. I can't find the correct Package.json file

• ABP Framework version: v6.0.2
• UI type:Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes

For our project we scan our source code during the pipeline build with the service MEND formerly known as WhiteSource. I use LeptonX in our project and the scan is finding a lot of javascript library vulnerabilities that the security team needs me to fix ASAP. The problem I see is, I don't seem to have much control over these files and how I can update them since they are apart of the LeptonX code base. Does anyone have any ideas of what I can do?

I am having the same issues. Any ideas?

Does anyone have any ideas?

• ABP Framework version: v6.0.1
• UI type: Blazor Server
• DB provider: EF Core

I am trying to add some basic components to the top toolbar in the LeptonX theme. I am just trying to start by adding a drop-down but cannot get it to show up. I added my own version of SideMenuLayout.Razor named MySideMenuLayout which inherits from SideMenuLayout. I think it has to do with where I am placing the files. I tried two places. First one was Themes\LeptonX\Components\ApplicationLayout. Second place was Components\ApplicationLayout\MySideMenuLayout.razor and MySideMenuLayout.razor.

Here is the razor file. 

@using Volo.Abp.AspNetCore.Mvc.UI.Components.LayoutHook

<div class="lpx-scroll-container ps">
	<div id="lpx-wrapper">
		<MainHeader />

		<div class="lpx-content-container">
			<div class="lpx-topbar-container">
                <div class="lpx-topbar">
                    <MainHeaderBranding />
                    <p>Select a Customer</p>
                    <Dropdown>
                        <DropdownToggle Color="Color.Primary">
                            Dropdown
                        </DropdownToggle>
                        <DropdownMenu>
                            <DropdownItem>UAT Customer</DropdownItem>
                        </DropdownMenu>
                    </Dropdown>
                    <Breadcrumbs/>
                </div>
			</div>
			<div class="lpx-content-wrapper">
				<div class="lpx-content">
					<ContentToolbar />
					<PageAlert />
                    @typeof(LayoutHooks.Body)
                    <DynamicLayoutComponent />
					<UiMessageAlert />
					<UiNotificationAlert />
				</div>
			</div>
		</div>

		<MobileNavbar />

		<div class="lpx-toolbar-container">
			<MainHeaderToolbar />
		</div>
	</div>
</div>

Here is the cs file

using System.Threading.Tasks;
using Microsoft.AspNetCore.Components;
using Microsoft.Extensions.Options;
using Microsoft.JSInterop;
using Volo.Abp.AspNetCore.Components.Web;
using Volo.Abp.DependencyInjection;
using Volo.Abp.LeptonX.Shared;


namespace Cure8.Blazor.Components.ApplicationLayout;

[ExposeServices(typeof(SideMenuLayout))]
[Dependency(ReplaceServices = true)]
public partial class SideMenuLayout : Volo.Abp.AspNetCore.Components.Web.LeptonXTheme.Components.ApplicationLayout.SideMenuLayout
{

}

Any updates on this?

The HandleErrorAsync(ex); is only in the BLazor component though. The issue I am having is getting the error from the server and actually getting all the way to the component. It is getting lost somewhere and not making it to the client to be handled by the HandleErrorAsync method.

• ABP Framework version: v6.0.0
• UI type: Blazor Server
• DB provider: EF Core

What is the best practice to return and show errors from the server side to be viewed in the client for a Blazor Server app? In other versions, I never had to worry about it. If I caught an exception, I could return UserFriendlyException and it would show a message in the client modal with no problem. But I can't seem to figure out something similar for Blazor Server. Any help would be much appreciated.

I think you are completely misunderstanding me or something. I did use that version. I tried to remove the sections for the language settings and it errors as I explained previously. That is not a fix for this, unfortunately.

Any updates on this?