Hi
I'm trying to drop a typed dataset onto a form. I choose DataSet from the toolbox and drop it on the form. Then, in the Add DataSet Wizard, I choose Typed Dataset, choose "Referenced Datasets" from the list, and then choose the dataset that I want. (The dataset is from another project in my solution.
This is supposed to work, but instead I get an error message that says "Could not add an instance of dataset ... to the designer. To resolve this problem, build the project, fix any errors, and add the instance to the designer again." The problem is, when I rebuild there are no errors, but it still does not work
Is this a known bug, and if so, what is the workaround
Thanks
John
John Rusk - 09 Jun 2004 07:01 GMT
Hmmm The bug mysteriously went away. I just tried using a dataset that was in the same project as the form. That worked, so then I tried using the original dataset, the one that caused the bug. Now, that _also_ works
John
Scott Fletcher - 08 Jul 2004 05:41 GMT
We, too, have been fighting this problem off-and-on for 6 months. Here is what I know about the general steps to reproduce.
1. Create a new solution (or edit an existing one)
2. Add a Class Library project to the solution to house some datasets, and add a dataset (xsd) to the project.
3. Add a new Class Library to the solution to house some Windows forms, and add a new Windows form to the project.
4. Add a reference in the Windows forms project to the datasets project.
5. Try to add a dataset to the newly-created windows form. Select "Referenced Datasets" in the "Add a Dataset" dialog box, and you will not see any of the referenced datasets; the list will be empty.
Usually when this happens, all I need to do is modify the dataset project and rebuild it. (Something about rebuilding the referenced project must regenerate whatever metadata the "Add a Dataset" dialog is reading?) But sometimes this does NOT fix the problem.
We also have a lot of problems with our Intellisense for referenced projects, and I suspect it is related. It really is a bummer.
The problem usually happens after adding a new project to the solution, and then
Scott Fletcher - 08 Jul 2004 05:47 GMT
One more fix seems to be closing the solution, exiting Visual Studio, and starting it again. That just worked for me again tonight. I'd sure like to know if this is a known issue and if it has been addressed in VS 2005.
---Scott