From: alexander.santos on
I am suffering from the same problem. It started happening when I added
a new column on a datatable on my dataset and build the dll with the
dataset.
When I opened the rdlc to refresh the website datasource it just
vanished.
I created a new web site (jst for test), added a reference to my dll
(with the dataset), added a new report. The website datasources where
there (with my dataset), when I changed the datatable including a new
column, the problem happened the same way.

If you wanna see it happening, just create a simple class project with
a typed dataset and then a website project with a rdlc and then see the
website datasources, then you change your dataset, build and try to
refresh the website datasources. I will reinstall my vs2005 and the
vs2005 sp1 (which I installed yesterday) while I wait for your answer
Mr. Cheng.

Thanks in advance and sorry about my english (I'm Brazilian)

Alexander M. Santos (MCAD)

From: cpnet on
I was not able to get the issue using the same process as Alexander, but I
am able to replicate this by doing the following:

- Create an assembly "DataSetAssembly.dll" which contains only a
strongly-typed DataSet, "MyDS". (No TableAdapters needed, I just have 3
DataTables and 1 Relation).
- Create a web project that references "DataSetAssembly.dll"
- Add a SQL Server Reporting Services report to the web project. You will
see the DataSet/DataTables defined in "DataSetAssembly.dll" listed as
Website Datasources, however, the first table is always imported twice. I
have 3 DataTables in my DataSet: Test1, Test2, and Test3. These are listed
as "MyNamespace.Test1", "Test1", "Test2", "Test3". So, there is a bug in
how VS is importing the DataTables since the first table (Test1) is listed
twice.
- Add a class to the webproject.
- Add a public method to the class that returns a new instance of the
"MyDS" DataSet, defined in "DataSetAssembly.dll". Despite the fact that
this method returns the whole DataSet "MyDS", this is listed in the Website
Datasources window as, "MyDS.Test1" (as if the method only returns the first
DataTable from the DataSet).
- Add a public method or property to the class that returns one of the
DataTables from the MyDS DataSet. The Website Datasources window will now
be empty.
- Create a new class in the web project that derives from MyDS. In this
test, doing this achieved nothing - my Website Datasources list is still
empty. In my original project/solution when I first noticed the problem,
doing this would cause the Website Datasources list to be populated.


From: Steven Cheng[MSFT] on
Hi cpnet,

Regarding on the behavior you mentioned in the last reply.

I think the first one:

====================
You will see the DataSet/DataTables defined in "DataSetAssembly.dll" listed
as Website Datasources, however, the first table is always imported twice.
===============

it is expected. Because this means that you can use a certain
DataTable(typed) as data source through two means.

1) directly reference to a DataTable's instance as datasource

2) reference to a typeDataSet which contains the DataTable. The reason why
the first item only contains DataSetName.FirstTable is because, the first
datatable is always the default member use to databind when you perform
databinding against DataSet(this is true for not only SSRS report, but also
normal ASP.NET databound control).

For the second issue, I have tested in my local environment and did
reproduce it.
================
Add a public method or property to the class that returns one of the
DataTables from the MyDS DataSet. The Website Datasources window will now
be empty.
==================

I'll perform some further research to see whether there is existing issue
on this and will update you as soon as possible.


Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.


From: Steven Cheng[MSFT] on
Hello Cpnet,

After some initial discussion with some other engineers, there seems hasn't
an existing documented issue on this. Since this is an obvious problem
behavior which impact the design-time user experience, I have helped you
submited a bug request on this internally. I'll wait for the product team
engineer's feedback on this. I'll closely monitor it and keep informing you
the latest information.

Thanks for your understanding.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


This posting is provided "AS IS" with no warranties, and confers no rights.

From: cpnet on
Sounds good... thanks.