Visual Studio 2005

Re: Problems with MSDataSetGenerator in VS.NET 2005 SP1

st_ — Fri, 16 May 2008 11:15:56 GMT

This problem such a disaster. I tried many ways, migrating xml data into another, making changes by hand.. etc. - very difficult because of having many table adapters. Finally I found a really strange generated query which was named GetDataBy1 and FillBy1. Then I remembered I received an error during generating one of my last queries. I think I've canceled it but obvioulsy some code has been generated. This code was the reason to receive this error.

This solved my porblem.

I recommend you to delete all last changes since last project saving or building.

Re: Problems with MSDataSetGenerator in VS.NET 2005 SP1

FredyC — Wed, 14 May 2008 11:17:12 GMT

Thank you very much man ! Your simple solution is really perfect and works well.

Re: Problems with MSDataSetGenerator in VS.NET 2005 SP1

EverettE — Thu, 24 Jan 2008 16:14:46 GMT

I have confirmed this exact same issue in VS2008 for web applications.

To get around it, I deleted the connection string I created in the project properties window. In the dataset designer, I click "New Connection..." when creating a new Table Adapter. This will for some reason only stick the connection string in the web.config file. From there, create your Table Adapter as you usually would. Back to your code behind window, you will now get intellisense on your dataset and table adapters.

I do not have this issue in VS2005 SP1 or VS2008 using WinForms. Weird.

Hope this helps.

Re: Problems with MSDataSetGenerator in VS.NET 2005 SP1

fhtino — Mon, 21 Jan 2008 08:26:24 GMT

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=321275

Re: Problems with MSDataSetGenerator in VS.NET 2005 SP1

anov — Mon, 08 Oct 2007 02:43:31 GMT

mself:
I had the same problem.

The issue turned out to be that the connection string is being stored in Properties.Settings, but the name of the setting has a dot in it (which causes problems).

I solved the problem by opening up the app settings editor and changing the name of the connection string setting from "MyAppName.Properties.Settings.XYZConnectionString" to simply "XYZConnectionString".

I'm not sure how the setting got the long name in the first place, but some MS tool must have set it that way (I didn't type it in myself).

Now when I got to create a DataSet using this connection string everything works correctly when I save it. I also had to edit some places in the code where I was referring to the connection string manually.

It appears that the Custom Tool that converts .xsd files to C# code cannot handle connection string names with dots in them. I think it is creating a property using the name of the connection string without escaping the dots. This causes parse errors when other parts of the code try to access that property.

i have a access db in app_data (samplenama.com) and renamed it (samplenama_com) change web_config connection string and change .xsd file with source file editor. error went out. removing dot (in the file name) solve my problem.

Re: Problems with MSDataSetGenerator in VS.NET 2005 SP1

Dimebrain — Mon, 13 Aug 2007 14:54:54 GMT

That's definitely the issue. I also had dots in my connection string which was generated for me when designing the typed datasets; it likely happens when you are prompted by the designer to add a new connection string, it adds the string to your Settings file but retains the full name when it added to your .config file. Thanks for that, this is a much cleaner workaround than referencing a custom sub-class. On the other hand the bug helped me make the switch to DLINQ :)

Re: Problems with MSDataSetGenerator in VS.NET 2005 SP1

mself — Mon, 13 Aug 2007 05:50:44 GMT

I had the same problem.

The issue turned out to be that the connection string is being stored in Properties.Settings, but the name of the setting has a dot in it (which causes problems).

I solved the problem by opening up the app settings editor and changing the name of the connection string setting from "MyAppName.Properties.Settings.XYZConnectionString" to simply "XYZConnectionString".

I'm not sure how the setting got the long name in the first place, but some MS tool must have set it that way (I didn't type it in myself).

Now when I got to create a DataSet using this connection string everything works correctly when I save it. I also had to edit some places in the code where I was referring to the connection string manually.

It appears that the Custom Tool that converts .xsd files to C# code cannot handle connection string names with dots in them. I think it is creating a property using the name of the connection string without escaping the dots. This causes parse errors when other parts of the code try to access that property.

Re: Problems with MSDataSetGenerator in VS.NET 2005 SP1

tmreis — Thu, 19 Jul 2007 10:57:09 GMT

Hey guys.I've been around this since yesterday. I had the MsDataSetGenerator problem, which I solved cutting the string from the Custom Tool Generator property. It compiled but then again I still need my Dataset to be generated.

All I want to do is have a DAL to a simple table. I've tried the VS2005 datasets and I even tried external code generators (ie: just tools that generate classes with CRUDs , all external to VS2005 IDE)

Even so I have a similar problem, in spite of the errors being different. I'll paste it here to see if I can get any help (maybe I'm just being rookie, but I have followed several tutorials on DAL and the code generation stuff and I never had this problem)

I should mention I have Biztalk 2006 installed, I don't know if this causes any kind of override.

My generated code is :

[System.ComponentModel.DataObjectMethodAttribute(System.ComponentModel.DataObjectMethodType.Insert, true)]

and the error is :

'string' does not contain a definition for 'ComponentModel'

As I said, the error is the same whether I use VS2005 Dataset or an external code generator. I guess the problem is with connection string management, but I just can't figure it out.

Thanx in advance,

Re: Problems with MSDataSetGenerator in VS.NET 2005 SP1

vidapura — Thu, 19 Jul 2007 08:18:18 GMT

Glad to be able to help,

Haven't reported it on Connect at all.. if you want to do the honours then please go right ahead...

Vida

Re: Problems with MSDataSetGenerator in VS.NET 2005 SP1

Dimebrain — Thu, 19 Jul 2007 03:32:48 GMT

Thanks so much for this; it claimed five or six hours of my life, but luckily I found your post. I still think someone needs to report this on Connect if you haven't already. Have you? Is there any feedback on this? We don't need another designer glitch in VS...

Re: Problems with MSDataSetGenerator in VS.NET 2005 SP1

vidapura — Thu, 07 Jun 2007 14:51:41 GMT

Great news!

Vida

Re: Problems with MSDataSetGenerator in VS.NET 2005 SP1

algorithm0 — Thu, 07 Jun 2007 14:40:09 GMT

vindapura,

Good news! After some wreckless messing around with my dataset I was able to get it to compile again. I ended up deleting the last table I had added a query to. Evidently the entire table was messed up, not simply the query on its table adapter. So now I am able to compile both my original app as well as the class library.

The one big lesson I'll take away from this is to keep my own versioning / backup at least once daily. I tried to roll back to monday's version of my code from tape, but the company's backp system wasn't configured to backup my particular directory... (oh the irony).

At least I was able to test out using a class library... I've been writing most of my recent code using a BLL for re-use, but I hadn't yet put it inside a library.

Now it's time to play catch-up on this project! Thanks for the thoughtful reply!

Re: Problems with MSDataSetGenerator in VS.NET 2005 SP1

vidapura — Thu, 07 Jun 2007 13:29:06 GMT

Hi there,

I sympathise, I had like 5 tables with 4 or queries each.. so i didn't want to go recreating the dataset either...

I only went the class library route because I wanted to have everything tidied away into a class library that I could reuse....you probably don't need to do that if you don't want to...

If you are just putting the xsd into a new project then I'd again create a quick dataset as normal.. and then copy over the connection string etc...

The method I detailed above worked for me... dunno what I can tell you to help... was there anything in my previous post that i could explain better?

What kind of project are you coming from and what kind are you going to?

Vida

Re: Problems with MSDataSetGenerator in VS.NET 2005 SP1

algorithm0 — Thu, 07 Jun 2007 13:01:05 GMT

I am having this problem too. Yesterday I tried vidapura's method of creating a class library, but I don't think it worked. The class library compiled, but I still go this warning:

Warning 1 The custom tool 'MSDataSetGenerator' failed while processing the file 'MyDataSet.xsd'.

I am still open to suggestions at this point. I'd really hate to have to re-create my entire dataset (7 tables, 30-some queries). I have check that my xml is well-formed. I have tried running MyDataSet.xsd through xsd.exe at the command prompt:

Writing file 'C:\Documents and Settings\xuser\My Documents\Visual Studio 2005\Projects\WebClassLibrary\MyDataSet.cs'.
Error: There was an error processing 'BoatDataSet.xsd'.
- Error generating code for DataSet ''.
- Failed to generate code. Object reference not set to an instance of an object.
- Object reference not set to an instance of an object.

Any advice is welcome! Thanks!

Re: Problems with MSDataSetGenerator in VS.NET 2005 SP1

vidapura — Wed, 06 Jun 2007 11:50:23 GMT

whoops, double post, can't delete it so I'll just edit it to this.