I´ve migrated a Prism WPF Application to .NET Core 3.1 but one project uses a WCF-Service which receives Http-Json-Post-Requests and I wasn´t able to find an alternative working in .NET Core 3 or .Netstandard...
In the previous .NET Framework version WCF calls published events by the IEventAggregator to execute EventHandlers in decoupled Prism modules...I tried to add a .NET Core Web Api project handling my HTTP requests but I could not host it in the Prism application or add my UnityContainer to the .NET Core Web Api project...does anyone have an idea how I can replace my WCF project with a .NET Core 3 project ?
Problem solved by self hosting ASP.NET Core in a separate netstandard2.1 project, registering the class containing the WebHost to the UnityContainer of the PRISM application and injecting the UnityContainer to be used by the WebHost as IServiceCollection.
Related
I just started with Authentication and authorization for SPAs of Dotnet core 3.0 by using
dotnet new angular -o <output_directory_name> -au Individual
and it created a new project with Angular as a client side app and ASP.net core as a backend. Now I want to use MySQL with this template.
I have tried using two providers for this
MySql.Data.EntityFrameworkCore
Pomelo.EntityFrameworkCore.MySql
but both of them are not supported with Entityframework core 3.0 and asking me to downgrade to Entityframework core 2.2. When I downgraded to Entityframework core 2.2 another package named Microsoft.AspNetCore.ApiAuthorization.IdentityServer starts breaking as it requires Entityframework core version 3.0 and above.
Can somebody please tell me how to setup this template of Authentication and Authorization for SPAs for MySQL?
It turned out I had to wait some time for Pomelo Entity Framework Team to release the .NET Core 3.0 Supported version which is available now. All the other things are now working as expected.
We have the multi-platform system which I need to communicate between node.Js and .net Core microservices with ESB. The system runs on premises.
We already started to use MassTransit in our .net services.
Is there a way to publish/consume messages with node.js using the MassTransit platform?
I have finally started my transition to .NET Core and need some quick help with getting to the environmentVariables section of the launchSettings.json file. Googling indicates pretty much all NetCore is currently ASP.NET Core whereas I'm currently spiking with libraries and console apps myself.
Is there no API for this?
launchSettings.json is a configuration file on how to launch ASP.NET Core applications. If you're looking for a .NET Core alternative to app.config for a console application, have a look at appSettings.json.
A (simple) example can be found here Using strongly typed configuration in .NET Core console app
how to integrate the SAP application to the web application which developed in polymer.
A common way that web applications integrate with SAP is using REST or SOAP webservices. Some of your options may depend on the version of the SAP Netweaver Application Server that you have.
You can create REST webservices using SAP Gateway which was incorporated in to the core of the Netweaver Application Server in version 7.4. Here is an overview of that https://blogs.sap.com/2013/01/24/a-simple-overview-on-sap-netweaver-gateway/
You can find more details on SOAP webservices from this wiki page https://wiki.scn.sap.com/wiki/display/ABAPConn/ABAP+Connectivity++-+Web+Services+ABAP.
As a part of my job, I need to add a new webservice to one our existing projects. Currently all of the services are ASMX webservices using WSE 3.0, but the new service needs to use WSE 2.0 SP3 because the vendor that will be calling it refuses to upgrade to 3.0.
I was hoping that someone here knew how to let these two versions run side by side.
Thanks
You will be unable to run both side by side. WSE 2.0 runs on the .NET 1.1 platform. WSE 3.0 runs on the .NET 2.0 platform.
You should be able to run WSE 3.0 on the web service and have the client use WSE 2.0 on their end. Both should implement the WS-Security standards respectively.