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.
Related
My application is hosted with JAVA 7. Hence need to have code sample for which is samples is with JAVA 7.
I can see the code with JAVA 8 or above.
https://github.com/Azure-Samples/ms-identity-java-desktop
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.
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.
I have a project developed on .NET Framework 2.0. Now I want to include an SSRS Report to this project but I am unable to find ScriptManager and ReportViewer controls in my toolbox. These are available in .NET Framework 4.0, so what do I have to do to create SSRS report for Framework 2.0
.Net Framework 2.0 was released ten years ago, so ideally you should look to upgrade to a more recent version. However if you are stuck with 2.0 then you will need to use the Report Viewer control from SQL Server 2005, which can be downloaded from the Microsoft website:
https://www.microsoft.com/en-us/download/details.aspx?id=21916
I was very hopeful that since SQL Server 2012 SQLCLR supports .NET 4.0 that SQL Server Reporting Services (SSRS) 2012 would support .NET 4.0 custom code assemblies. When attempting to upload an rdl (via the Report Manager or via RSBuild) that references .NET 4.0 assemblies, the Reports Manager throws an error stating
This assembly is built by a runtime newer than the currently loaded
runtime and cannot be loaded. (rsErrorLoadingCodeModule)
Is there something I can configure to get SSRS 2012 to load .NET 4.0 assemblies? Will we be waiting until the next major release of SQL Server before we see .NET 4.0 support for custom assemblies in SSRS?
SSRS 2014 is now released and custom code still does not support the .Net 4.0 Framework.
See prerequisites in the "Hardware and Software Requirements for Installing SQL Server 2014"
(http://msdn.microsoft.com/en-us/library/ms143506(v=sql.120).aspx)
It's very amusing that SQL Server 2014 has just RTM'ed a few days ago and is already considered a "legacy application" by the .Net Framework guys who say:
.NET Framework 3.5 is not included by default in Windows 8 or Windows
Server 2012, but you can download and deploy it for legacy application
compatibility.
... see "Microsoft .NET Framework 3.5 Deployment Considerations"
(http://technet.microsoft.com/en-us/library/dn482066.aspx)
I think the bigger issue is whether the support lifecycle of .Net 3.5 SP1 can actually be tied to the OS'es for which it was a default component. Whatever they say, I can't see Microsoft quitting support on .Net 3.5 as long as SQL Server continues making it a prerequisite in a product they are releasing today. The .Net Framework guys can't be too happy with the lazy SQL guys right now...
Actually, I find that reports using .Net 4.0 assemblies will work fine in VS 2010 (PreviewProcessingService.exe)...
And the reports may also work for you when deploying them to SSRS 2012 SP1 in SharePoint 2013 integrated mode.
Here is the authoritative answer on when/where the .Net 4.0 CLR is supported by SSRS: http://support.microsoft.com/kb/2869522/en-us
For those of us who use SSRS in standalone mode (without SharePoint), we might be stuck on the .Net 2.0 CLR for a while.
I might be wrong and there might be more differences but having compared reports downloaded from reporting services and "identical" ones made in Visual Studio using .Net framework 4.0+ I think the only difference is that puts a ReportParametersLayout section in the xml. If you manually remove this from the xml version of the report file then upload hopefully it will work for you