We are wondering why some projects are .NET standard and others .NET 6.
We think we need make references from Application to several .NET 6 projects, we can off course 'upgrade' the Module 'Application' project to .NET 6 but we're not sure why it is a .NET standard project and what the consequences of this upgrade would be.
Are the .NET standard projects there for compatibility reasons, so they can be referenced by other type of solutions or platforms ?
Can you explain the reason behind that?
Kind regards, Jurjen.
Module:
Application .NET standard
Application.Contracts .NET standard
Blazor .NET 6.0
Blazor.WebAssembly .NET 6.0
Domain .NET standard
Domain.Shared .NET standard
EntityFramework .NET 6.0
HttpApi.Client .NET standard
HttpApi .NET 6.0
Application:
Application .NET 6.0
Application.Contracts .NET standard
Blazor .NET 6.0
DbMigrator .NET 6.0
Domain .NET 6.0
Domain.Shared .NET standard
EntityFramework .NET 6.0
HttpApi .NET 6.0
HttpApi.Client .NET standard
HttpApi.Host .NET 6.0
If you're creating a bug/problem report, please include followings:
We'd like to be able to, on the fly, retrieve an object from DI/IOC. In our situation it's not possible to do this through injection in the class constructor.
With ASP.NET Zero we could use IocManager.Resolve<type>
Is something similar possible with ABP.IO
kind regards, Jurjen.
Good afternoon,
We’re experiencing some problems when using CSLA.NET (https://cslanet.com/)with your product (commercial).
In project HttpApi.Host we are using a DataPortalController (api-controller) wich does NOT inherit from AbpController. This controller can be used from various clients to retrieve Csla-businessobjects.
We’ve been prototyping this in the beginning of Q2 using ABP.IO v4.3 and back then it worked fine.
Last week we picked up where we left of in April and for some reason it doesn’t work anymore. We’re getting errors in the HttpApi.Host project (see Error-StackTrace in logs.txt below)
We’ve spent several days chasing this problem and we think there’s some middleware or ‘hook’ into the http pipeline which tries to change something in the response.
We’ve isolated the CSLA.NET in a separate solution, not using ABP.IO, just a regular WebApi Core project in combination with a regular Blazor client and that works fine. We think that there’s something in the ABP http-pipeline causing this. Maybe it’s the ABP-Auditing? (We tried to disable auditing for this controller with [DisableAuditing] attribute but that doesn't seem to make a difference, still throws an exception)
We were wondering if you could help us in locating the problem (and resolving the problem) as you’re far more familiar with how http works in ABP.IO.
Flow:
[BlazorClient] BusinessObject Person
[BlazorClient] Person.Get(23) // Get person where Id =23
[BlazorClient] Remote DataPortal is called over http https://localhost:<port>/DataPortal
[HttpApi] Call is received, Fetch is called on BusinessObject Person
[HttpApi] Normally the Fetch will do a DB call but in this example we just fill properties with
some fixed values.
[HttpApi] When the response is sent/returned from the DataPortal to the requesting client it
seems that there is ‘something’ wich interveens and somehow causes a problem.
As you can see in the log (in StepsToReproduce.PDF), the controller-method PostAsync is successful after wich something is done resulting in ‘Added 0 entity changes to the current audit log’ (twice) and the an exception occurs.
As we cannot attach files I've created a weTransfer link : <Removed> This download contains the example code + database backup and StepsToReproduce.PDF If the link has expired, please contact me via info@idas.nl for a new link of I can send the files to you directly.
Please don't hesitate to contact me if you cannot reproduce the problem or if you're having questions.
Kind regards
Jurjen de Groot Idas BV
I'm looking into creating some BackgroundJobs. How to create them and how to use the args is pretty straight forward I guess but it's not clear to me in wich (application or module) project the backgroundjobs should be created.
I guess not in the UI, EF or DB-related projects, but could you indicate for application and for module where to create these classes ?
Application
Application.Contracts
Domain
Domain.Shared
HttpApi
HttpApi.Client
{Application}.HttpApi.Host
I have read the documentation and see examples of how to use and enqueue the job but WHERE to create these jobs is not in the documentation. Maybe this could be added to the documentation for future use?
Kind regards, Jurjen.
https://docs.abp.io/en/abp/latest/Background-Jobs https://docs.abp.io/en/abp/latest/Modules/Background-Jobs (= TODO)
• ABP Framework version: v4.3 rc1 • UI type: Blazor • DB provider: EF Core • Identity Server Separated: no • ABP Commercial application
When running the blazor application locally I can see that calls to the HttpApi.Host have a httpheader Authorization with value ‘bearer ’.
<br> We will be using Csla as our businesslogic/data-layer for our application. Csla uses a ‘dataportal’ to retrieve data from the database, this dataportal call routes through the dataportalcontroller on the WebApi and is visible in swagger (https://localhost:44321/api/Blazor/DataPortal) just like all the other Abp methods like AbpApiDefinition (https://localhost:44321/api/abp/api-definition).
Csla ‘calls’ the DataPortal using its own httpClient, however thát httpclient does not have a defaultHttpHeader ‘Authorize’ we get an not-authorized error when calling the DataPortal method on the WebApi. We have been testing and when we sort of manually add defaultHttpHeader Authorize with the token to the httpClient when calling the DataPortal, it doés work :-)
I’m not sure but can we ‘get’ a ready to go (authorized) httpClient from ABP? I’ve tried using
[Inject] public HttpClient httpClient {get;set;}
But there is no ‘Autorize’ DefaultHttpHeader supplied in the resulting httpClient.
At this time we’d like to ask:
I have downloaded the easy-crm Sample application. Unzipped, followed the steps as explained on this page: https://docs.abp.io/en/commercial/latest/samples/easy-crm
Then I open the solution and run Volo.EasyCrm.Web, I log in to that application, then from VS-2019 I start the Volo.EasyCrm.Blazor project, The login page appears, I log in, then the screen goes gray and the nice 'C' keeps rotating.... that's where things stop working.
I have searched the docs / samples / support forum couldn't find a solution there.
I'm not sure what going wrong but this is one of the warnings I get.
** Could not find IdentityClientConfiguration for . Either define a configuration for or set a default configuration.
And then at the end there's this Exception: Unhandled exception rendering component: VTable setup of type Blazorise.Snackbar.SnackbarStack failed
The MVC application is working just fine, but the Blazor application is failing.
Can anyone shed some light on this problem ?
Kind regards, Jurjen
--- Debug output ---
info: System.Net.Http.HttpClient.AbpMvcClient.LogicalHandler[101]
End processing HTTP request after 179.9099ms - 200
'iisexpress.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App\5.0.3\Microsoft.AspNetCore.Metadata.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
warn: Volo.Abp.IdentityModel.IdentityModelAuthenticationService[0]
Could not find IdentityClientConfiguration for . Either define a configuration for or set a default configuration.
info: System.Net.Http.HttpClient.AbpMvcClient.LogicalHandler[100]
Start processing HTTP request GET https://localhost:44338/api/abp/application-configuration?api-version=1.0
info: System.Net.Http.HttpClient.AbpMvcClient.ClientHandler[100]
Sending HTTP request GET https://localhost:44338/api/abp/application-configuration?api-version=1.0
info: System.Net.Http.HttpClient.AbpMvcClient.ClientHandler[101]
Received HTTP response headers after 50.8899ms - 200
info: Microsoft.AspNetCore.Authorization.DefaultAuthorizationService[2]
Authorization failed. These requirements were not met:
PermissionRequirement: EasyCrm.Countries
: /__w/1/s/src/mono/mono/metadata/loader.c:1964 <disabled>
crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
Unhandled exception rendering component: VTable setup of type Blazorise.Snackbar.SnackbarStack failed
System.TypeLoadException: VTable setup of type Blazorise.Snackbar.SnackbarStack failed
at System.Reflection.RuntimeConstructorInfo.InternalInvoke(Object obj, Object[] parameters, Boolean wrapExceptions)
at System.RuntimeType.CreateInstanceMono(Boolean nonPublic, Boolean wrapExceptions)
at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean wrapExceptions, Boolean skipCheckThis, Boolean fillCache)
at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, Boolean wrapExceptions)
at System.Activator.CreateInstance(Type type, Boolean nonPublic, Boolean wrapExceptions)
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at Blazorise.ComponentActivator.CreateInstance(Type componentType)
at Microsoft.AspNetCore.Components.ComponentFactory.InstantiateComponent(IServiceProvider serviceProvider, Type componentType)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.InstantiateComponent(Type componentType)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.InstantiateChildComponentOnFrame(RenderTreeFrame& frame, Int32 parentComponentId)
at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InitializeNewComponentFrame(DiffContext& diffContext, Int32 frameIndex)
at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InitializeNewSubtree(DiffContext& diffContext, Int32 frameIndex)
at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InsertNewFrame(DiffContext& diffContext, Int32 newFrameIndex)
at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.ComputeDiff(Renderer renderer, RenderBatchBuilder batchBuilder, Int32 componentId, ArrayRange`1 oldTree, ArrayRange`1 newTree)
at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.RenderInExistingBatch(RenderQueueEntry renderQueueEntry)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()
crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
Unhandled exception rendering component: No element is currently associated with component 12
Error: No element is currently associated with component 12
at e.updateComponent (https://localhost:44307/_framework/blazor.webassembly.js:1:31696)
at Object.t.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:12129)
at Object.window.Blazor._internal.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:61899)
at Object.w [as invokeJSFromDotNet] (https://localhost:44307/_framework/blazor.webassembly.js:1:64421)
at _mono_wasm_invoke_js_blazor (https://localhost:44307/_framework/dotnet.5.0.0.js:1:190800)
at wasm_invoke_iiiiii (<anonymous>:wasm-function[5611]:0xdda7c)
at ves_pinvoke_method (<anonymous>:wasm-function[5708]:0xdfb5f)
at interp_exec_method (<anonymous>:wasm-function[2155]:0x44c05)
at interp_runtime_invoke (<anonymous>:wasm-function[7861]:0x12efed)
at mono_jit_runtime_invoke (<anonymous>:wasm-function[7346]:0x118e4d)
Microsoft.JSInterop.JSException: No element is currently associated with component 12
Error: No element is currently associated with component 12
at e.updateComponent (https://localhost:44307/_framework/blazor.webassembly.js:1:31696)
at Object.t.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:12129)
at Object.window.Blazor._internal.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:61899)
at Object.w [as invokeJSFromDotNet] (https://localhost:44307/_framework/blazor.webassembly.js:1:64421)
at _mono_wasm_invoke_js_blazor (https://localhost:44307/_framework/dotnet.5.0.0.js:1:190800)
at wasm_invoke_iiiiii (<anonymous>:wasm-function[5611]:0xdda7c)
at ves_pinvoke_method (<anonymous>:wasm-function[5708]:0xdfb5f)
at interp_exec_method (<anonymous>:wasm-function[2155]:0x44c05)
at interp_runtime_invoke (<anonymous>:wasm-function[7861]:0x12efed)
at mono_jit_runtime_invoke (<anonymous>:wasm-function[7346]:0x118e4d)
at Microsoft.JSInterop.WebAssembly.WebAssemblyJSRuntime.InvokeUnmarshalled[Int32,RenderBatch,Object,Object](String identifier, Int32 arg0, RenderBatch arg1, Object arg2, Int64 targetInstanceId)
at Microsoft.JSInterop.WebAssembly.WebAssemblyJSRuntime.InvokeUnmarshalled[Int32,RenderBatch,Object](String identifier, Int32 arg0, RenderBatch arg1)
at Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer.UpdateDisplayAsync(RenderBatch& batch)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()
crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
Unhandled exception rendering component: No element is currently associated with component 18
Error: No element is currently associated with component 18
at e.updateComponent (https://localhost:44307/_framework/blazor.webassembly.js:1:31696)
at Object.t.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:12129)
at Object.window.Blazor._internal.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:61899)
at Object.w [as invokeJSFromDotNet] (https://localhost:44307/_framework/blazor.webassembly.js:1:64421)
at _mono_wasm_invoke_js_blazor (https://localhost:44307/_framework/dotnet.5.0.0.js:1:190800)
at wasm_invoke_iiiiii (<anonymous>:wasm-function[5611]:0xdda7c)
at ves_pinvoke_method (<anonymous>:wasm-function[5708]:0xdfb5f)
at interp_exec_method (<anonymous>:wasm-function[2155]:0x44c05)
at interp_runtime_invoke (<anonymous>:wasm-function[7861]:0x12efed)
at mono_jit_runtime_invoke (<anonymous>:wasm-function[7346]:0x118e4d)
Microsoft.JSInterop.JSException: No element is currently associated with component 18
Error: No element is currently associated with component 18
at e.updateComponent (https://localhost:44307/_framework/blazor.webassembly.js:1:31696)
at Object.t.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:12129)
at Object.window.Blazor._internal.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:61899)
at Object.w [as invokeJSFromDotNet] (https://localhost:44307/_framework/blazor.webassembly.js:1:64421)
at _mono_wasm_invoke_js_blazor (https://localhost:44307/_framework/dotnet.5.0.0.js:1:190800)
at wasm_invoke_iiiiii (<anonymous>:wasm-function[5611]:0xdda7c)
at ves_pinvoke_method (<anonymous>:wasm-function[5708]:0xdfb5f)
at interp_exec_method (<anonymous>:wasm-function[2155]:0x44c05)
at interp_runtime_invoke (<anonymous>:wasm-function[7861]:0x12efed)
at mono_jit_runtime_invoke (<anonymous>:wasm-function[7346]:0x118e4d)
at Microsoft.JSInterop.WebAssembly.WebAssemblyJSRuntime.InvokeUnmarshalled[Int32,RenderBatch,Object,Object](String identifier, Int32 arg0, RenderBatch arg1, Object arg2, Int64 targetInstanceId)
at Microsoft.JSInterop.WebAssembly.WebAssemblyJSRuntime.InvokeUnmarshalled[Int32,RenderBatch,Object](String identifier, Int32 arg0, RenderBatch arg1)
at Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer.UpdateDisplayAsync(RenderBatch& batch)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()
info: Microsoft.AspNetCore.Authorization.DefaultAuthorizationService[2]
Authorization failed. These requirements were not met:
DenyAnonymousAuthorizationRequirement: Requires an authenticated user.
info: Microsoft.AspNetCore.Authorization.DefaultAuthorizationService[2]
Authorization failed. These requirements were not met:
DenyAnonymousAuthorizationRequirement: Requires an authenticated user.
crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
Unhandled exception rendering component: No element is currently associated with component 5
Error: No element is currently associated with component 5
at e.updateComponent (https://localhost:44307/_framework/blazor.webassembly.js:1:31696)
at Object.t.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:12129)
at Object.window.Blazor._internal.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:61899)
at Object.w [as invokeJSFromDotNet] (https://localhost:44307/_framework/blazor.webassembly.js:1:64421)
at _mono_wasm_invoke_js_blazor (https://localhost:44307/_framework/dotnet.5.0.0.js:1:190800)
at wasm_invoke_iiiiii (<anonymous>:wasm-function[5611]:0xdda7c)
at ves_pinvoke_method (<anonymous>:wasm-function[5708]:0xdfb5f)
at interp_exec_method (<anonymous>:wasm-function[2155]:0x44c05)
at interp_runtime_invoke (<anonymous>:wasm-function[7861]:0x12efed)
at mono_jit_runtime_invoke (<anonymous>:wasm-function[7346]:0x118e4d)
Microsoft.JSInterop.JSException: No element is currently associated with component 5
Error: No element is currently associated with component 5
at e.updateComponent (https://localhost:44307/_framework/blazor.webassembly.js:1:31696)
at Object.t.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:12129)
at Object.window.Blazor._internal.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:61899)
at Object.w [as invokeJSFromDotNet] (https://localhost:44307/_framework/blazor.webassembly.js:1:64421)
at _mono_wasm_invoke_js_blazor (https://localhost:44307/_framework/dotnet.5.0.0.js:1:190800)
at wasm_invoke_iiiiii (<anonymous>:wasm-function[5611]:0xdda7c)
at ves_pinvoke_method (<anonymous>:wasm-function[5708]:0xdfb5f)
at interp_exec_method (<anonymous>:wasm-function[2155]:0x44c05)
at interp_runtime_invoke (<anonymous>:wasm-function[7861]:0x12efed)
at mono_jit_runtime_invoke (<anonymous>:wasm-function[7346]:0x118e4d)
at Microsoft.JSInterop.WebAssembly.WebAssemblyJSRuntime.InvokeUnmarshalled[Int32,RenderBatch,Object,Object](String identifier, Int32 arg0, RenderBatch arg1, Object arg2, Int64 targetInstanceId)
at Microsoft.JSInterop.WebAssembly.WebAssemblyJSRuntime.InvokeUnmarshalled[Int32,RenderBatch,Object](String identifier, Int32 arg0, RenderBatch arg1)
at Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer.UpdateDisplayAsync(RenderBatch& batch)
at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()
crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
Unhandled exception rendering component: No element is currently associated with component 5
Error: No element is currently associated with component 5
at e.updateComponent (https://localhost:44307/_framework/blazor.webassembly.js:1:31696)
at Object.t.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:12129)
at Object.window.Blazor._internal.renderBatch (https://localhost:44307/_framework/blazor.webassembly.js:1:61899)
at Object.w [as invokeJSFromDotNet] (https://localhost:44307/_framework/blazor.webassembly.js:1:64421)
at _mono_wasm_invoke_js_blazor (https://localhost:44307/_framework/dotnet.5.0.0.js:1:190800)
at wasm_invoke_iiiiii (<anonymous>:wasm-function[5611]:0xdda7c)
at ves_pinvoke_method (<anonymous>:wasm-function[5708]:0xdfb5f)
at interp_exec_method (<anonymous>:wasm-function[2155]:0x44c05)
at interp_runtime_invoke (<anonymous>:wasm-function[7861]:0x12efed)
at mono_jit_runtime_invoke (<anonymous>:wasm-function[7346]:0x118e4d)
Microsoft.JSInterop.JSException: No element is currently associated with component 5