ASP.NET-5 with EF6 - entity-framework-6

Is it possible to use the new ASP.NET with Entity Framework 6 instead of Entity Framework v7?
I use the latest Visual Studio 2015 and could not add a Ado.Net Data Model but the Reference to EF6 was added.

Most existing packages, such as EF6, will not support asp.net Core 5; because of the significant differences, they need to be manually updated. If you're wanting to use EF6 you'll need to stick to asp.net 5 (not Core).
I've run into a series of issues running the EF6 package manager commands, such as Add-Migration, in VS2015 CTP6; I believe they're still working on updates. I was able to get them working in a .Net 4.5 library that is referenced by my .Net 5 libraries, but I've found that occasionally I have to uninstall and install EF6 again to get the package manager commands working.

Related

EntityFramework (database first) using Azure managed identity for SQL DB

I'm in the process of converting the existing .Net framework project that uses EF 6 with Database First approach (EDMX) file to .Net Standard 2.1 which connects to SQLDB hosted on Azure.
Existing EDMX file has a constructor (auto generated) that accepts ConnectionString as given below -
public TestDatabaseConnection()
: base(ConfigurationManager.ConnectionStrings["TestDatabaseConnection"].ConnectionString)
{
}
This is breaking for two reasons -
ConfigurationManager.ConnectionStrings works only in .Net framework projects and throw runtime errors in the .Net Core project (for eg- ConfigurationManager.ConnectionStrings returns null).
I need to make changes to the above code to use the AppAuthentication nuget as mentioned in the MSDN docs here
So, what are the options available in order to make this work so that I could use the same nuget package for connecting to the database via EF 6 (database first) for both .net framework and .net core projects?
Is the only available is to convert to Code first and make the necessary changes as mentioned in the above MSDN link?

.Net Core Vs .Net framework to create a new mvc web application

I have visual studio 2015 professional editton, and i want to create my first MVC web application which should be a .net core. now i am watching an online learning demo, which mentioned to create this project:-
while inside my visual studio i have these options:-
so which option i need to chose?
second question, how i can be sure that i am using the latest version of MVC?
Thanks
First, there is no such thing as MVC 6. It's ASP.NET Core. Second, the decision of whether to use .NET Core or .NET Framework comes down to what you need to do. .NET Core is cross-platform (Windows, Mac and Linux), whereas .NET Framework is Windows-only. .NET Core is also lighter weight, faster, and has a number of new CLR features, compared to .NET Framework. Virtually the only reason to use .NET Framework is if you have a dependency on something that utilizes Windows-specific APIs, meaning it can't be run cross-platform. Otherwise, you should always use .NET Core, if you can get away with it.
ASP.NET Core is really just a collection of NuGet packages, and like other NuGet packages, they can be updated easily. However, the difference is that these NuGet packages are generally tied to a particular version of .NET Core, and thus, the appropriate version of the packages are installed based on which version of .NET Core you're targeting. For example, if you're targeting netcoreapp2.2 then you'll see that that packages like Microsoft.AspNetCore.App will be brought in with versions like 2.2.x.
So, to answer your question about staying up to date, it essentially entails installing the latest version of the .NET Core SDK, and then changing your project to target that new version. Then, all the ASP.NET Core NuGet packages will naturally update accordingly.

Syntaxlistpool.free separated syntax builder. While scaffolding Asp.Net Core 2.1

All packages are update till today, and using EF Core Code first. But while scaffolding API controller.
Syntaxlistpool.free separated syntax builder. While scaffolding
Asp.Net Core 2.1
Check the version of Microsost.CodeAnalysis.Common referenced in your project. I had version 2.9.0 but needed 2.8.0. Microsoft.CodeAnalysis.Workspaces.Common requires version 2.8.0. If you have the same problem then you will see this error in Visual studio's NuGet reference.
I would also recommend ensuring visual studio, asp.net core, .net core are up to date

AspNetZero - .NET Core 2.0 MVC Version - Error on adding new controller

After about 6 months, I returned to work on my AspNetZero solution based on .NET Core 2.0.
I have the original downloaded version and the modified version as separate GIT repositories. In both versions/repositories when I try to add a new MVC controller, I keep getting the below error message.
On my PC I have all of the .NET Core SDKs installed from 1.0 right up to 2.1.302. I have other projects that I am working on, where I'm using .NET Core 2.1.
I even created a brand new .NET Core 2.0 project in VS2017 and I am able to scaffold a new MVC controller without any errors. This issue is only happening on the AspNetZero solution.
I have done many searches for a solution and none of the answers I found online have worked. I just added a global.json file into my solution folder and set the SDK to 2.0.0 and tried again, still does not work. I keep getting the same error!
Your NuGet packages may have been invalid according to your
target framework. Check all your recent NuGet packages for .NET Core
versions.
Clear your NuGet cache as shown in the picture
Update: Delete all bin & obj folders.

Upgrade MVC1 project to MVC5

Is there a way to convert a ASP.Net MVC 1 project build in VS2008 to ASP.Net MVC 5 and VS2015?
I tried to just open it in VS 2015 but that gave the error "This project is incompatible with the current version of Visual Studio".
There are ways to reference newer versions and update, eg:
http://www.asp.net/mvc/overview/releases/how-to-upgrade-an-aspnet-mvc-4-and-web-api-project-to-aspnet-mvc-5-and-web-api-2
.. however updating from MVC1 (especially if you cannot open the project) you probably don't want to manually install ASP.NET MVC installs etc (if that what I remember)
I would suggest creating a new MVC5 application, referencing MVC via Nuget etc and pulling in code as required. This will give you a chance to re-structure things and learn newer ways otherwise you my be fighting with MVC configuration and references.

Resources