Problem with typed dataset

[Harry Strybos]

Visual Studio 2005 - SP1 - VB.Net on WinXP SP2

I add a typed dataset to my solution and get the following errors :

Error 1 sub 'ReadXmlSerializable' cannot be declared 'Overrides' because it
does not override a sub in a base class.
C:\AAProjects.Net\TRM8\TRM8.UI\Reports\BillingReport.Designer.vb 125 29
TRM8.UI

Error 2 'Protected Overrides Function GetSchemaSerializable() As
System.Xml.Schema.XmlSchema' cannot override 'Protected Overridable Function
GetSchemaSerializable() As System.Xml.Schema.XmlSchema' because they differ
by their return types.
C:\AAProjects.Net\TRM8\TRM8.UI\Reports\BillingReport.Designer.vb 145 34
TRM8.UI

I have a reference to System.Xml.

If I start a new project, and add a typed dataset, this error does not
occur.

Can anyone help me with this frustrating problem.

TIA

 

[RobinS]

How are you adding the typed dataset to your solution?

Robin S.

 

[Harry Strybos]

How are you adding the typed dataset to your solution?

Robin S.

Project/Add New Item/Dataset......

The whole thing is then built by the IDE. Error appears immediately. Adding
an actual query (Sql 2005) via Server Explorer does not make the problem go
away

 

[RobinS]

Project/Add New Item/Dataset......

The whole thing is then built by the IDE. Error appears immediately.
Adding an actual query (Sql 2005) via Server Explorer does not make
the problem go away

What is your dataset called? Are you calling it something that already
exists somewhere within your sollutino? The errors above are from
BillingReport.Designer.vb -- is BillingReport the name of your dataset?
Is it something else within your project?

Robin S.

 

[Harry Strybos]

What is your dataset called? Are you calling it something that already
exists somewhere within your sollutino? The errors above are from
BillingReport.Designer.vb -- is BillingReport the name of your dataset? Is
it something else within your project?

Robin S.

"BillingReport" is the name of the dataset.
That name or type does not exist elsewher in my solution. I di try this with
the same solution in my home office and the same problem occurs.

Just to add to all of this, I do have some reasonable experience with VS
2005, as IT Manager of an SME.

Thank you.

 

[RobinS]

"BillingReport" is the name of the dataset.
That name or type does not exist elsewher in my solution. I di try
this with the same solution in my home office and the same problem
occurs.

Just to add to all of this, I do have some reasonable experience with
VS 2005, as IT Manager of an SME.

I wasn't assuming you were a newbie; we all make these kinds of mistakes
once in a while, and it never hurts to doublecheck.

Does it only happen when you add that specific dataset? Are you choosing
a table in your database? Does it work when you pick a different table?

Robin S.

 

[Harry Strybos]

I wasn't assuming you were a newbie; we all make these kinds of mistakes
once in a while, and it never hurts to doublecheck.

Does it only happen when you add that specific dataset? Are you choosing a
table in your database? Does it work when you pick a different table?

Robin S.

My apologies. I wasn't trying to be beligerent. And you are quite right, we
all make some obvious mistakes from time to time.

I am able to reproduce this problem on a seconf development machine at my
home office. It seems there is something in my application (some 50 forms)
that is corrupting a reference somewhere. Interestingly, on one other
programmers machine, he can load my application and add a typed dataset
without error, yet when I load his update, the error reoccurs on my machine.
So, one machine does not show this error at all, two show it all the time
and one shows it in my application but not in a new project.

I have seen the same problem reported elsewhere but have not been able to
see any solutions. Searching the web with either of the error messages does
produce some results but no answere.

As I mentioned previously, the error occurs even before I assign a query or
table. While I am sure it is a bug (my other programmers have checked this
as well), there seems to be no apparent solution.

Perhaps somebody else may have the answer.

Cheers

 

[Harry Strybos]

My apologies. I wasn't trying to be beligerent. And you are quite right,
we
all make some obvious mistakes from time to time.

I am able to reproduce this problem on a seconf development machine at my
home office. It seems there is something in my application (some 50 forms)
that is corrupting a reference somewhere. Interestingly, on one other
programmers machine, he can load my application and add a typed dataset
without error, yet when I load his update, the error reoccurs on my
machine.
So, one machine does not show this error at all, two show it all the time
and one shows it in my application but not in a new project.

I have seen the same problem reported elsewhere but have not been able to
see any solutions. Searching the web with either of the error messages
does
produce some results but no answere.

As I mentioned previously, the error occurs even before I assign a query
or
table. While I am sure it is a bug (my other programmers have checked this
as well), there seems to be no apparent solution.

Perhaps somebody else may have the answer.

Cheers

Found the answer, thanks to a fellow called Todd M. Taylor :

So, I've think that my solution file had something wrong or there was
something in one of my projects that affect the other ones. The only strange
project was that one that had no errors. So I've removed it and the errors
magically disappeared. Adding project again errors started to appear again.

I've opend my project file with notepad and I've found that System.Xml
reference was written in this way:
<Reference Include="System.Xml, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
<HintPath>..\..\..\..\..\..\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll</HintPath>
</Reference>

I've changed this reference with this:
<Reference Include="System.Xml" />

.... and magically everything worked.

Cheers

 

[RobinS]

Found the answer, thanks to a fellow called Todd M. Taylor :

So, I've think that my solution file had something wrong or there was
something in one of my projects that affect the other ones. The only
strange project was that one that had no errors. So I've removed it
and the errors magically disappeared. Adding project again errors
started to appear again.

I've opend my project file with notepad and I've found that System.Xml
reference was written in this way:
<Reference Include="System.Xml, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>

<HintPath>..\..\..\..\..\..\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll</HintPath>
</Reference>

I've changed this reference with this:
<Reference Include="System.Xml" />

... and magically everything worked.

Cheers

Cool! Thanks for letting us know.

Robin S.