|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Provider TracingGreetings,
I followed the instructions on MSDN for enabling the provider tracing but it does not trace anything. Is there a simpler set of instructions (that are appplicable to the RTM version of the ADO.NET instead of Beta1) and that might possibly consider WinXP instead of only Win2k3 (the MSDN uses syntax and switches that aren't available on the RTM). Thanks, Shawn Does nobody know the answer to this question?
> I followed the instructions on MSDN for enabling the provider tracing but Thanks,> it does not trace anything. Is there a simpler set of instructions (that > are appplicable to the RTM version of the ADO.NET instead of Beta1) and > that might possibly consider WinXP instead of only Win2k3 (the MSDN uses > syntax and switches that aren't available on the RTM). Shawn > I followed the instructions on MSDN for enabling the provider tracing but Three weeks and not a single response. I'm quickly becoming convinced that > it does not trace anything. Is there a simpler set of instructions (that > are appplicable to the RTM version of the ADO.NET instead of Beta1) and > that might possibly consider WinXP instead of only Win2k3 (the MSDN uses > syntax and switches that aren't available on the RTM). this feature is either a) not supported in the final release or b) not a single person in the world uses the feature. So, here's to hoping someone knows how to use the ADO.NET 2.0 Provider Tracing features. The article: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnadonet/html/tracingdataaccess.asp Is out of date and on three different computers (that are not similar in configuration) absolutely nothing happens, even when compensating for the differences between Beta 1 and RTM as well as the fact that I'm running WinXP instead of Win2k3 (in the article). Thanks, Shawn |
|||||||||||||||||||||||