I am working on an Asp.Net Core 1.0 + EF Core 1.0 (RC2 targeting net46) project which will be deployed in Azure and relying on SQL Azure for data.
I know that EF Core 1.0 doesn't plan to support Connection Resiliency for v1.0
Is it possible to support connection resiliency through some other means?
.Net 4.5.1 added built-in support for connection resiliency in ADO.NET. Since EF is built on top of ADO.NET does it mean that it's already included?
There are a number of improvements in that area in .net 4,6,1, but true Command execution resiliency is still on th EF Core roadmap
Related
I have created a worker service to consume my eventhub data and save that into cosmos db. But I want to deploy my worker service with my web app which is an .net core web application.
Can anyone help me out here to get my job done ?
What architecture I should follow for it?
UPDATE
Upgrade Visual Studio Enterprise 2019（Version 16.7.7） to the latest version, the problem still exists.
After my test (using Visual Studio Enterprise 2019 16.0.30406.217 D16.7), I found that when you add Existing Project as Azure Webjob to the webapp of the .net framework, it can be successful.
But I cannot add it to the webapp of .net core. I think this is a bug.
Suggestions can raise a support ticket to confirm and seek official help.
I have a machine with installed DNX (beta-8) and running ASP.NET 5-beta8 API Service. And what I need is to publish another one API service, that have been created using ASP.NET Core 1.0.
So I'm worried if I do not break the current old Service if I install .NET Core Tooling on this machine.
Unfortunately, I don't have an option to update old API Service to ASP.NET Core 1.0
Yes, you should be able to run dnx and dotnet side by side but it's not an officially supported scenario. The only known issue is that you cannot have VS tooling that supports both. However, if you build/publish from console, it should work.
That being said, dnx is deprecated and it will not updated in the future.
Is there a Production ready Persistence provider for JPA 2.1? I see that Hibernate is only going to support it only from 4.3 onwards and its only in a beta stage.
Im using eclipselink 2.5.1. http://www.eclipse.org/eclipselink/. Seems to work stable.
We have a bunch of ASP.NET apps written in .NET 2.0 (with IIS6 ASP.NET version set to 2.0), visible via Virtual Directories within one website deployed to Windows Server 2003. Does anyone know whether we can set the ASP.NET version within IIS, of all of these to 4.0 without breaking the (.NET 2.0) applications - i.e. no other changes other than within IIS
Any official Microsoft link(s) stating this can be done, would be brilliant also
You should avoid such "big changes". ASP.NET 1.x, 2.0 and 4.0 applications should be separated and held in standalone application pools.
Besides, there are too many breaking changes in ASP.NET 4 compared to previous versions, you should carefully migrate when the time is right,
http://www.asp.net/learn/whitepapers/aspnet4/breaking-changes
I know that SharePoint 2010 uses .net 3.5 and since .net 2 (3.5 with sp1) has different CLR than .net 4, what is the best practice to use Entity Framework 4 (4.2) with it?
Is the web service (WCF service) the only solution for it?
If not, what is the best ORM similar to EF from simplicity and productivity prospective is recommended to use to connect to MS SQL Server? (may support oracle later)?
Is the web service (WCF service) the only solution for it?
Yes. You have to do cross process call because your main process is .NET 3.5 and you need another process running .NET 4.0.
What is the best ORM similar to EF from simplicity and productivity prospective is recommended to use to connect to MS SQL Server? (may support oracle later)?
Other alternatives are for example NHibernate or LLBGen Pro. Both are supported in .NET 3.5. You can also try Linq-To-Sql or SubSonic.