Configure MySQL with EFcore 3.0 - mysql

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.

Related

Microsoft.SqlServer.Management.IntegrationServices reference in .net core 2.1?

I'm trying to create a service to run dtsx packages in .net core 2.1. In .net framework you could reference using Microsoft.SqlServer.Management.IntegrationServices which would allow you to connect to Sql Server and run dtsx packages. Is there a way to reference that in .net core 2.1?

using MySql.Data; not working with .NET Framework 4.6

I load the reference MySql.Data and verify that this is loaded.
I place
using MySql.Data;
into my code, but it cannot find MySql.Data.
There are many versions of MySql.Data available and many solutions indicated for this in previous posts.
One possible cause is that the .NET Framework version is incompatible with the version of the MySql Connector/NET.
Check your version of the .NET Framework, since the Connector/NET only works up to .NET Framework 4.5.x and changing the version from 4.6 to 4.5.2 worked for me. (Project > Properties > Application > Target Framework).
REFERENCE: MySQL Versions

Unable to Deploy SQLCLR Project

My first SQLCLR project is resisting all attempts to deploy...
I get the error
The following error might appear if you deploy a SQL CLR project that
was built for a version of the .NET Framework that is incompatible
with the target instance of SQL Server: "Deploy error SQL01268: CREATE
ASSEMBLY for assembly failed because assembly failed verification". To
resolve this issue, open the properties for the project, and change
the .NET Framework version.
C:...\SqlClr.dll : Deploy error : Could
not create a type for parameter MyModel.Customer customer
The command
select * from sys.dm_clr_properties
returns
directory C:\Windows\Microsoft.NET\Framework64\v2.0.50727\
version v2.0.50727
state CLR is initialized
The Target framework for the project is .NET Framework 2.0
The object referenced in the error message MyModel.Customer is included in the SqlClr project via a Link (Add Existing Item / Add as Link) from another project that is using .NET Framework 4.0, but my understanding is the other project's .NET version should have no bearing.
What might I be missing?
If you are referencing an assembly that is dependent upon .NET 4.0, you're likely in for trouble. My understanding is that SQLCLR assemblies must be based on .NET versions 2.0 through 3.5, because versions 2.x and later prior to 4.0 are really just extensions based on 2.0. That tends to coincide with some information I read recently about an explicit decision for the SQLCLR not to support Framework 4.0.

Which version of WebSphere is best for JSF2.0 web dev with PrimeFaces3.1

I am newbie with WebSphere. Recently I downloaded WebSphere Community Edition version 3 (WASCE v3) but there is no description about using WASCE v3 with JSF2.0 in the guide "Getting started with WASCE". I already build my web in Apache Tomcat 7.0.11 with JSF2.0 and PrimeFaces 3.1. I am using eclipse INDIGO. Now i have to shift my server to WebSphere. Please suggest me the best version of WebSphere, which is suitable for JSF2.0 with PrimeFaces3.1?
Thank you.
WASCE 3 is a Java EE 6 container, so it has support for JSF 2.0 (if it wouldn't have this, it couldn't be called Java EE 6).
Do note that people typically don't mean WASCE when they refer to WebSphere. WASCE is another name for the server otherwise known as Apache Geronimo. The difference is that it's specifically supported by IBM.
What people do mean with WebSphere is the one you can find here: ibm.com/software/webservers/appserv/was
For JSF 2.0 you would need the latest version, which is version 8.

How can you interop WSE 2.0 and 3.0 in a single project

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.