We have an aspx project developed in entity framework 3-tier architecture. This is an ERP and we already developed 3 to 4 modules of it.
Now we have changed our mind and want to develop the remaining modules in MVC 5. What is the best way to convert the existing project to mvc5, so that we can continue the remaining modules with mvc.
Also is it possible to run entity framework 3-tier inside mvc5, it will be like 3 to 4 modules of the same application will be entity and remaining will be mvc5.
Related
I have created a new application, using the SPA templare of .netcore, to this solution i want to add another project to handle the database connection(DAL).
When i am adding ASP.net core Web Application to this solution, i then want to add to id an ADO.net entityframework template, but in the data section, it dont appear:
So I end-up adding a class Library(.net framework)
and to it i can add an ADO.net Entity Data Model
So now in the solution, i have 2 projects, 1 is .net core 2.1 for the API's, models and views(by angular).
The second project is a .net framework 4.6.1, class library project.
My question is, is it suppose to be like that?
is it a good thing to mix different frameworks
Please see this article regarding what each framework is, and what each is specifically designed for.
https://learn.microsoft.com/en-us/dotnet/standard/frameworks
In a nutshell, your requirements drive which framework you choose.
I would recommend sticking with EF Core (just my personal opinion, take it or leave it) The EF Core method of database first is only recommended if you require a 1 time migration from a source database. Microsoft Doc
If you need to CONTINUE working with an entity model past the first migration, it would be in your best interest to use Entity Framework 6, on a .NET Framework library like you have. But that doesn't stop you from using EF Core as your OR/M, because you can indeed have .NET Core reference .NET Framework.
We're trying to bring an ASPNET MVC 5 solution to ASPNET Core cause we have directions to move to Azure Service Fabric for production.
Given that a way to get an MVC web site running into Service Fabric, is to use a Self Hosting tech like ASPNET Core (running on top of full .NET Framework), from our existing codebase we'd like to change just the MVC pieces of our solution, leaving the rest as is wherever possible.
These two pieces must remain untouched because of reducing change workload, but most, for customizations on top (mostly for Identity)
Entity Framework 6 (tested and good to go)
ASPNET Identity 2 (Multitenancy & Custom Password hashing must be left unchanged -this project has been ported since ASPNET Membership days, and its actively running in prod since then-)
The issue: ASPNET Identity 2 and its compatibility into the ASPNET Core stack.
Being an OWIN stack player, we're finding hard to make use of it into ASPNET Core's Configure() (for piping) and ConfigureServices() (for DI)
Anyone out there going thru something alike?
Dotnet core does not use Entity Framework 6 It Uses Entity Framework Core and asp identity core these two are much alike but they are slightly different from asp net MVC.
all configurations are done in Startup.cs in core.
https://learn.microsoft.com/en-us/aspnet/core/migration/mvc?view=aspnetcore-2.1
Please use this as reference for migrating your code.
Is there any way to use Entity Framework in vNext MVC 6 (in the current release). Well, I found no option in "Add new item" of VS14 ctp and if we do manually there is some DB update problems (as i tried in earlier versions) and whats the neuget package available for Entity Framework and oData and how to use them. Please help
There is not yet support for OData in ASP.NET vNext, but there is a new version of Entity Framework: EF7. You can learn more about getting started with Entity Framework 7 here: https://github.com/aspnet/EntityFramework/wiki
I'm asking because I'm working on an ASP.NET MVC 1.0 site, thinking of upgrading to ASP.NET MVC 2.0. Then I read that PLINQO 5.0 was released (I had never heard of PLINQO before) and have been impressed with what PLINQO appears to be capable of.
1) Is PLINQO capable of building out an ASP.NET MVC 2.0 UI project when it's run?
2) Have you had any bad experiences using PLINQO (particularly in an ASP.NET MVC app)?
Let me make sure I have the scenario right in my mind:
Using PLINQO (assuming it supports ASP.NET MVC 2.0), I should be able to point it to my DB and it will create 3 projects: data, test, and mvc 2.0 UI? The data would contain LINQ to SQL queries, with the PLINQO extensions added in and the other projects setup to use the data project by default?
I'm exploring PLINQO 5.0 and here are my answers,
1) No, PLINQO will not build MVC2 UI Project. But the Data project supports MCV2, take a look the latest Traker sample application.
2) No and still a better choice comparing to EF4.
HTH
I have a standard template "ASP.NET MVC 2 Web application" solution, an empty (meaning no data inserted, but with all tables etc. ready and waiting) SQL Server database, an Entity Framework 4 model (edmx). Is there a way to generate simple CRUD controllers and form views for all the entities in the model?
A buddy out there helped me with the answer - the answer is to use a "ASP.NET Dynamic Data Entities Web Application" instead of "ASP.NET MVC 2 Web Application" project template. The rest is 1-2-3-easy and is explained here: http://msdn.microsoft.com/en-us/library/cc488469.aspx
Hmm. His question was how to do this with MVC, not .NET.
I too would like to hook up and generate MVC user forms from a Sql Server schema.