Re: ADO.NET SQLConnection Best Practices
- From: "Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx>
- Date: Fri, 22 Feb 2008 16:45:55 -0500
DJB-CT wrote:
I've opened a ticket with PSS regarding intermittant ADO.NET SQL
errors ( SRX080221600812).
There was no way for you to know it (except maybe by browsing through some
of the previous questions in this newsgroup before posting yours - always a
recommended practice) , but this is a classic ADO newsgroup. ADO.Net bears
very little resemblance to classic ADO so, while you may be lucky enough to
find a dotnet-knowledgeable person here who can answer your question, you
can eliminate the luck factor by posting your question to a group where
those dotnet-knowledgeable people hang out. I suggest
microsoft.public.dotnet.framework.adonet.
While reviewing our code, the PSS engineer stated that ADO.NET 2.0
SQLConnection objects at the class level are a bad idea and
SQLConnections should not be passed as method parameters, but I have
not been able to find whitepapers confirming the recommendations.
Are there whitepapers that explain where a SQLConnection, with code
samples?
Thanks in advance.
I think you should look at Data Access Application Block here:
http://msdn2.microsoft.com/en-us/library/aa480453.aspx
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"
.
- Prev by Date: Re: ADODB.Recordset (0x800A0E78) Operation is not allowed when the object is closed.
- Next by Date: Begin Tran open disconnected recordset - reconnect - rollback/comm
- Previous by thread: ADODB.Recordset (0x800A0E78) Operation is not allowed when the object is closed.
- Next by thread: Begin Tran open disconnected recordset - reconnect - rollback/comm
- Index(es):
Relevant Pages
|
Loading
