ADO.Net DBConnection Visualizer
by codemonkey » Thu, 27 Jul 2006 10:45:36 GMT
Hey Folks,
I've just finished an initial version of a de{*filter*} visualizer for
Visual Studio 2005 that allows you to hover over an ADO.Net connection
object and run quick SQL statements against it and see the results in a
grid. Any feedback is much appreciated.
The add-on dll can be found at http://www.**--****.com/
To install, simply copy the dll to "My Documents\Visual Studio
2005\Visualizers"
I've only tried it with the SQLite provider for ADO.Net
( http://www.**--****.com/ ), but it should work with any type of
database connection that derives from System.Data.Common.DBConnection.
Let me know what you think (please reply to this post or use the
SourceForge project forums).
Cheers,
Trev.
Similar Threads:
1.Newbie Questions on ADO.NET in VB.NET(basically ADO.NET questions)
ok. I have a basic understanding of the dataset but still more questions
than answers.
For example, if you use the Server Explorer to create connections, and then
wizards to generate datasets...
1.) What if this is an app that you will redistribute and not a corporate
app where these connections are fixed? What do those GUI representations
really mean in terms of code and how do you allow the user to change where
that connection points--I.e. computername, sqlservername, database name
,etc.
2.) Isn't a dataset a lot of overkill? I get this dataset and load it with
separate tables with tons of data so that I don't have to reconnect to the
database--that is the purpose right? Then if that is a lot of data that is
a lot of network traffic and client memory used up right? Also if I get
just a portion of the data then if I want more I must hit the database again
anyway. Also, if I make updates then I have to write code to try to deal
with collisions.
What do you do if User A enters a lot of stuff and then User B does two...
both try to update the dataset to the database and one gets failures--does
that mean I tell him... sorry all your work for the last 30minutes couldn't
be done and dump it?
I guess I just don't get it.. Seems like a whole lot more work than
benefit. I have seen a few instances where I could see the dataset being
useful--like getting a bunch of data to just display and sort etc. But when
it comes to adding data etc. Seems teh direct approach with sqlcommands and
stored procs is more sensible.
Then do you just create a dataset for the whole project and use the same one
for each form--is it globally available, or is the xsd file just a spec that
I use to create a new one in each form as needed?
Am I totally lost here?
Any ideas would be appreciated. As you can see I know enough to be
dangerous but still fail to get the big picture and think that it all has to
be easier than what I can see and that also these GUI items in the IDE like
the Server Explorer have to make life easier... But I honestly haven't been
using it so far for my connections--just code--because I know what that does
and how to allow the user to change it.
Thanks,
Shane
2.ASP.Net cache Debugger Visualizer?
3.newbie vb6 ADO to vb.net ado.net, paging
4.differences between ado.net and ado.net 1.1
hello!,
please, can anyone tell me the differences betwwen these 2 versions?... i
just find comparisons between ado.net 2.0 and ado.net 1.1
thanks a lot.
5.VB.net/ADO.net ADO Wrapper....
Hi,
I'm just about to write one of these components to simplify simple dataset
return, and command execution against a SQL Server database.
Does ANYONE have a component freely available that I can use? This will save
me a day or two!
Cheers :)
--
Liddle Feesh
*fap fap fap fap*
<>< <>< <>< <>< ><>
<>< <>< <>< <>< <>< <><
6. Serialized ADO.NET 1.0 dataset compatible with ADO.NET 2.0
7. Converting code ADO VBA to ADO net VB.net
8. ADO.NET 2.0 vs ADO.NET 1.1