How to display the VS.NET Add/Modify Connection dialog at runtime

[Polaris431]

An article is available on how to display the VS.NET 2005 Add/Modify
Connection dialog at runtime. The article shows how you can include
this dialog in your applications to allow users to establish a
connection to any data source and data provider and create the
connection string at runtime. The article is located at:

http://www.filt-air.com/tools/cs-mat...on_dialog.aspx

Best Regards
Johann Blake

[Marc Gravell]

Have checked, and it definitely isn't in the REDIST list...

Make your own enquiries, but I suspect you may be on thin ice if somebody
audited this usage... and note that this is an MS-hosted NG...

Marc

[Marc Gravell]

It would be interesting to see what the licence says about re-deploying part
of VS.Net...

Marc

[Polaris431]

Many software developers have absolutely no respect for such
"licensing". That's a fact of life. If it solves the problem, they'll
use it. The chances of anyone at Microsoft even investigating a company
for some obscure usage of a DLL function is so remote that many
developers wouldn't even think twice about not using it. The fact is,
that the more something becomes used, the more likely Microsoft will
take notice and eventually include it in the packaging. Including a
connection dialog in your app should have been addressed years ago by
Microsoft. There will always be "good" hackers who the rest of us
should be grateful for.

Best Regards
Johann
On Nov 20, 2:46 pm, "Marc Gravell" <[e-mail]:

Have checked, and it definitely isn't in the REDIST list...

Make your own enquiries, but I suspect you may be on thin ice if somebody
audited this usage... and note that this is an MS-hosted NG...

Marc

[Marc Gravell]

I see your point, and agree with some (not all) of it...

I can't recall whether this dialog is part of C# express (all my
machines have both installed, so I can't verify). While this wouldn't
change the licence, you could also argue that it was a step in the
direction of being more free.

However, the point I was trying to make is that some organisations have
(by necessity) strict compliance rules (including licensing), and that
perhaps a disclaimer would be useful. Of course, and coder in such an
org. would know to check ;-p

"eventually" isn't "now". Just 'cos it's Bill, doesn't mean we can all
nick his code ;-p
And using an exposed API isn't really hacking - just disregarding the
Ts&Cs.

But I do see your point, and I do see the value of a connection dialog.

Marc