|
W∴ Balboos wrote: did he mean he was not nice or wasn't a people?
Et tu, Brutus?
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
So, @OriginalGriff is nice, after all. It's just that we don't know what species he is. 
|
|
|
|
|
My generosity and charity toward the human [fill in] condition knows no bounds!
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
|
That depends. Does your house have a nuclear shelter?
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
I've already asked here. 
I was pointed at a page that describes how to use dapper instead of EF. I don't want to use another ORM. I want to use our existing ADO code.
The only thing I use EF for is the Identity stuff. Everything else uses our own ADO code. Our (16) apps can be run in one of eight servers, and access over 20 databases, and *all* DB access is done via stored procs - except for the Identity stuff... It would be really convenient if we didn't have to use EF anywhere in the app.
".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
|
|
|
|
|
In our application (angular in nature) we use a MVC based login page, for witch we wrote our own Identity Provider (no EF here or everywhere else) - it was very easy to tell application to use it...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
#realJSOP wrote: So I posted a question on the Microsoft developer forums asking...
well that's where you went wrong right there.
unless you want to brag about how many ms certs and awards you have there's nothing there.
anyway, as suggested from MS forums: run SFC/SCANNOW run as a user with administrative priveledges* if doesn't work go ahead and reinstall windows**.
* need any help with how to run programs as administrator?
** need help on reinstalling windows? I've got 10 whole pages dedicated to that.
Look at my medals: https://i.dailymail.co.uk/i/pix/2009/12/06/article-1233634-0778DECD000005DC-737_224x423.jpg[^]
Message Signature
(Click to edit ->)
|
|
|
|
|
Lopatir wrote: Look at my medals
DSO and 2 bars, MC and bar. What a dude!
|
|
|
|
|
|
B*****d. Recently discovered that my dad was recommended for the MC, for real active service, but never received it, as he did not go to the right school. Snobbery really was rife in the 40s.
|
|
|
|
|
"there's nothing there."
that's for damn sure.  The last time I made the mistake of going out to MS forums, I saw a thread that went something like this:
User: Hi, I just updated to the latest Windows 10 on my Surface Pro 3. I'm now idling at 25% cpu, and it's killing my batter life.
MS rep: You need to scan your Surface for viruses. Also, make sure you have the latest drivers from the manufacturer.
User: Are you an idiot? I scanned the machine for viruses, and MS is the maker.
MS rep: nonplussed and doesn't miss a beat - you may need to do a clean re-install.
Don't even get me started on SO. Ask a question and get it instantly closed. I miss usenet. You had real smart people that had clues. I think some of them are hear on CP.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
It's quite common in forums in general that you ask a question about X and in effect are told use Y instead. What they overlook is even if Y is better than X they don't know your context. You may have existing code using X that it would be uneconomic and risky to rewrite using Y. Or in fact you may just happen to be maintaining some legacy code that uses X.
Or, Y may just be newer but not necessarily "better" than X and everyone on the team is well-versed in X but not Y.
Kevin
|
|
|
|
|
THey are useless, all they are interested in is getting points by replying, with some useless crap like going to windows update, or reinstalling the OS.
They are morons.
|
|
|
|
|
|
You talk about ADO, but please consider that EF is newer and has great support.
It's regularly updated and easy to use.
There is no case for ADO anymore.
Please see also the scenario for MVC5 where you can scaffold controllers using EF.
MVC stands for Model-View-Controller and you should separate your business logic from your views and your data layer from your BL.
Speaking of which, F# has great features which allow for great multi-threading code and because of its immutable nature you do not need to worry about race conditions.
But really in conclusion you should switch to Python.
Here is a link you can use: Java tutorial: Learn Java Programming with examples[^]
Please mark this as the accepted answer and don't forget to upvote.
Also, I downvoted your question because you didn't mention which version of PHP you're using.
|
|
|
|
|
I downvoted you because you didn't mention his SQL Injection problem.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Sander Rossel wrote: There is no case for ADO anymore.
Absolute statements are NEVER correct! 
|
|
|
|
|
Only a Sith deals in absolutes...
Yes, yes... Let the hate flow through you 
|
|
|
|
|
Sander Rossel wrote: You talk about ADO, but please consider that EF is newer and has great support.
You mean the kind of support where Microsoft says they're not going to fix reported bugs in EF6 - as far back as 2011?
Sander Rossel wrote: It's regularly updated and easy to use.
Regularly, as in only major revisions that require even more .Net bloatware be added to your app?
Sander Rossel wrote: There is no case for ADO anymore.
If that's the case, why did Microsoft recently announce that ADO.Net had been ported over to .Net Core?
I was ready for all of those statements. 
".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
|
|
|
|
|
Too bad you stopped there 
Well, I guess things started deteriorating even further after that
|
|
|
|
|
EF wouldn't, couldn't even, exists without ADO... 
I mean I am not 100% sure what he means by ADO. But for me, ADO is just the SqlConnection, SqlCommand, SqlParameters classes...
|
|
|
|
|
Yeah, that's ADO, ActiveX Data Objects.
Technically it's the common base classes and interfaces so that each database has uniform access and so the database can be swapped without hassle.
In practice, switching databases mid-project is always a hassle because they all work slightly different.
|
|
|
|
|
You write a "wrapper"? (data repository; DAL)
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
Yeah, I have a DAL that is inherited by a database-specific BLL that is called from various locations in the app.
The DAL exposes four public methods that use generics and reflect to populate the specified object
public List<T> ExecuteStoredProc<T>(string storedProc, params SqlParameter[] parameters)
public int ExecuteStoredProc(string storedProc, params SqlParameter[] parameters)
public List<T> ExecuteQuery<T>(string query, params SqlParameter[] parameters)
public int ExecuteQuery(string query, params SqlParameter[] parameters)
There's a BLL for each database that contains (or will contain) a method for each stored proc for that database. Usage goes like this:
DBObjectDBName dbo = new DBObjectDBName(Globals.ConnectionStrings.GetConnectionSTring("DBName");
List<MyDataModel> model = dbo.ExecuteStoredProc<MyDataModel>("dbo.StoredProcName", parameters (if any));
I have a base Controller class where I can create a property to create the DBObject instance, thus reducing the usage block to a single line in the outward facing code. One of these days, I'm going to write an article about it.
I don't need EF watching over me. I know how to write code.
".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
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
