Well, it was a complete pain...
-
But I think I've managed to eliminate entity framework from my MVC5 (.Net Framework) app, but keep the user management functionality so I can have single-user authentication, and use my own DAL/connection string manager code in the process. It compiles, so it's on to seeing if I did it right.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
But I think I've managed to eliminate entity framework from my MVC5 (.Net Framework) app, but keep the user management functionality so I can have single-user authentication, and use my own DAL/connection string manager code in the process. It compiles, so it's on to seeing if I did it right.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Quote:
It compiles, so it's on to seeing if I did it right.
You're experienced enough to know that 90% of the work probably lies ahead. :laugh:
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.<p><a href="https://github.com/GregUtas/robust-services-core/blob/master/README.md">Robust Services Core</a>
<em>The fox knows many things, but the hedgehog knows one big thing.</em></p> -
Quote:
It compiles, so it's on to seeing if I did it right.
You're experienced enough to know that 90% of the work probably lies ahead. :laugh:
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.Yah. I'm already running into issues... :/
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
But I think I've managed to eliminate entity framework from my MVC5 (.Net Framework) app, but keep the user management functionality so I can have single-user authentication, and use my own DAL/connection string manager code in the process. It compiles, so it's on to seeing if I did it right.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013what' wrong with EF btw?
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
what' wrong with EF btw?
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
- Footprint is too big (5-7mb of code). My own DAL assembly is less than 50k, and my identity assembly is less than 30k. Yes, I still have to ship 970k in MS assemblies to get it to "go", that's a far cry smaller from the EF footprint. 1) It really doesn't like stored procs. I, on the other hand, really like to use stored procs. and I've almost never encountered a CRUD-only back-end, so just relying on CRUD is a waste of resources. 2) I don't want it to deal with its migration strategies (if I think I need a table, I'll create the table) 3) The EF for .Net Framework is no longer being maintained by MS 4) Because 'murrica.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Quote:
It compiles, so it's on to seeing if I did it right.
You're experienced enough to know that 90% of the work probably lies ahead. :laugh:
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.- My first one was that I was using the wrong table names in my identity code (this was a mere forehead slapper). 1) Now I'm dealing with weirdness in the UserTable. Not difficult issues, but certainly tedious...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
- Footprint is too big (5-7mb of code). My own DAL assembly is less than 50k, and my identity assembly is less than 30k. Yes, I still have to ship 970k in MS assemblies to get it to "go", that's a far cry smaller from the EF footprint. 1) It really doesn't like stored procs. I, on the other hand, really like to use stored procs. and I've almost never encountered a CRUD-only back-end, so just relying on CRUD is a waste of resources. 2) I don't want it to deal with its migration strategies (if I think I need a table, I'll create the table) 3) The EF for .Net Framework is no longer being maintained by MS 4) Because 'murrica.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Quote:
It compiles, so it's on to seeing if I did it right.
You're experienced enough to know that 90% of the work probably lies ahead. :laugh:
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.Registration and login works.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
0.) 5-7MB vs 50K You are still using 9600bps connections? 1.) Same here, I don't like them ;P 2.) Correct 3.) .net framework will sooner or later disapear 4.) Pls. translate :laugh:
- Footprint has nothing to do with the speed of the connection because it's all server side, but it does consume space on the server file system. I happen to think it's excessive. 4) Translation - "Because America". :)
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
- Footprint has nothing to do with the speed of the connection because it's all server side, but it does consume space on the server file system. I happen to think it's excessive. 4) Translation - "Because America". :)
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013I used to count megabytes when I had 16MB of ram. Now my apps consume images in that range.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
I used to count megabytes when I had 16MB of ram. Now my apps consume images in that range.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
I'm old school. When I started programming 8k of ram was considered to be a lot, and disk space was no more than 320k. However, the foot print isn't the worst part of EF, it just happens to be the thing I thought of first.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
- Footprint has nothing to do with the speed of the connection because it's all server side, but it does consume space on the server file system. I happen to think it's excessive. 4) Translation - "Because America". :)
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
But I think I've managed to eliminate entity framework from my MVC5 (.Net Framework) app, but keep the user management functionality so I can have single-user authentication, and use my own DAL/connection string manager code in the process. It compiles, so it's on to seeing if I did it right.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
to be honest - wtf? Is this just web elephanting dookie?
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
I honestly don’t understand your question.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
- Footprint is too big (5-7mb of code). My own DAL assembly is less than 50k, and my identity assembly is less than 30k. Yes, I still have to ship 970k in MS assemblies to get it to "go", that's a far cry smaller from the EF footprint. 1) It really doesn't like stored procs. I, on the other hand, really like to use stored procs. and I've almost never encountered a CRUD-only back-end, so just relying on CRUD is a waste of resources. 2) I don't want it to deal with its migration strategies (if I think I need a table, I'll create the table) 3) The EF for .Net Framework is no longer being maintained by MS 4) Because 'murrica.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013#realJSOP wrote:
my identity assembly is less than 0k
Wow! Either you've invented negative code, or your assembly is so big it's overflowed the Windows "file size" counter. :laugh:
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
I honestly don’t understand your question.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013" entity framework from my MVC5 (.Net Framework) app, but keep the user management functionality so I can have single-user authentication, and use my own DAL/connection string manager code" The buzzwords tossed around completely lost me. So, when I saw your response, I decided to google to help me better understand what you are doing. :)
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
#realJSOP wrote:
my identity assembly is less than 0k
Wow! Either you've invented negative code, or your assembly is so big it's overflowed the Windows "file size" counter. :laugh:
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
I'm that good... :) (I fixed it.)
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
" entity framework from my MVC5 (.Net Framework) app, but keep the user management functionality so I can have single-user authentication, and use my own DAL/connection string manager code" The buzzwords tossed around completely lost me. So, when I saw your response, I decided to google to help me better understand what you are doing. :)
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
The template-generated code for a MVC5 project requires entity framework for the identity stuff (registration/login). Entity Framework doesn't play well with stored procs. It's possible to do (from what I hear), but it's a relative pain in the ass. When Entity Framework decides your database has changed, its "migration" policies can actually cause you to lose data. As far as I know, you can't completely turn off the migration features in EF (honsetly, if that has changed, I'm still not interested). I have a well-vetted DAL (that easily supports stored procs, and query text) and a much more versatile connection string manager that I like to use, not to mention an app I use to generate models from the database, so I don't need the crap that EF does. I think MS should have made the MVC5 project template configurable as far as whether to use an ORM (and which ORM), or a homegrown DAL class such as the one I'm using. I'm old and set in my ways, and don't need Microsoft to help me access my database by forcing me to use Entity Framework. BTW, I have in fact confirmed that I've completely eradicated Entity Framework from my project.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
The template-generated code for a MVC5 project requires entity framework for the identity stuff (registration/login). Entity Framework doesn't play well with stored procs. It's possible to do (from what I hear), but it's a relative pain in the ass. When Entity Framework decides your database has changed, its "migration" policies can actually cause you to lose data. As far as I know, you can't completely turn off the migration features in EF (honsetly, if that has changed, I'm still not interested). I have a well-vetted DAL (that easily supports stored procs, and query text) and a much more versatile connection string manager that I like to use, not to mention an app I use to generate models from the database, so I don't need the crap that EF does. I think MS should have made the MVC5 project template configurable as far as whether to use an ORM (and which ORM), or a homegrown DAL class such as the one I'm using. I'm old and set in my ways, and don't need Microsoft to help me access my database by forcing me to use Entity Framework. BTW, I have in fact confirmed that I've completely eradicated Entity Framework from my project.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013"I'm old and set in my ways, and don't need Microsoft to help me access my database by forcing me to use Entity Framework." If I ever migrate back to web development, it will be a cold day in hell (or someone is going to have to make it worth my while). I've read the various posts over the years of the buzzword lingo of various tool sets and what not. From an engineering point of view, depending on MS to support anything until the next "new shiny" comes along is a recipe for grief. And your comments are interesting - rather than have some EF or other tool generate a framework, come up with something stable and stick with it.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
"I'm old and set in my ways, and don't need Microsoft to help me access my database by forcing me to use Entity Framework." If I ever migrate back to web development, it will be a cold day in hell (or someone is going to have to make it worth my while). I've read the various posts over the years of the buzzword lingo of various tool sets and what not. From an engineering point of view, depending on MS to support anything until the next "new shiny" comes along is a recipe for grief. And your comments are interesting - rather than have some EF or other tool generate a framework, come up with something stable and stick with it.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
charlieg wrote:
And your comments are interesting - rather than have some EF or other tool generate a framework, come up with something stable and stick with it.
My DAL code is going on 10 years old now... I tweak it every now and then, but it's served me well.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
