Drag Once w/Custom Controls


Article written for CoDe magazine describing how to customize the controls listed in the Data Sources Window for Drag Once Databinding


http://www.code-magazine.com/Article.aspx?quickid=0411071


Steve

Comments (2)

  1. Diego Vega says:

    Steve, sorry if this is out of topic for the post (it is not for the blog), but I found no better means to ask you this question: ¿What the requirements are for an ADO.NET provider to be supported in by the DataSet designer and generator at design time?

    We have had our own ADO.NET provider that is actually a thin wrap for any other ADO.NET provider, and we have used this in the past to achieve database independence. Now we are rewriting our provider to use DBProviderFactory internally and we are seeing a huge improvment. The idea is to make it work with your DataSet designer, as a workaround, until MS devises a better way to target multiple database engines from the same dataset.

    In other words, it would be a workaround for this: http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=4320e4f2-964f-4ffb-9d7d-bbd5099fbfbc

    Thanks!

  2. Diego Vega says:

    Sorry if I sent duplicate comments, but the first one didn’t show up here.

    This is out of topic for the post, but on topic for the blog. I found no better means to ask you this question: ¿What the requirements are for an ADO.NET provider to be supported in by the DataSet designer and generator at design time?

    We have had our own ADO.NET provider that is actually a thin wrap for any other ADO.NET provider, and we have used this in the past to achieve database independence. Now we are rewriting our provider to use DBProviderFactory internally and we are seeing a huge improvment. The idea is to make it work with your DataSet designer, as a workaround, until MS devises a better way to target multiple database engines from the same dataset.

    Thanks!