Error in typed dataset : The custom tool 'MSDataSetGenerator' failed while processing the file '....file1.xsd'

Question

0.00/5 (No votes)

See more:

I have a typed dataset Data.xsd in a class library. Code compiles and I was able to publish it without any issues.

Today morning I tried to publish it and the publish failed with 101 warnings and 0 error messages.

One warning message I could catch was
"Warning 1 The custom tool 'MSDataSetGenerator' failed while processing the file 'DataModel\Persistence\DOCacheDS.xsd'."

Other warnings were for unused variables etc. and can be ignored for now. I always had them in the project.

I googled a lot and tried all the solutions mentioned but could not make it work.

I tried:
1. Removing and adding the dataset property "Custom Tool: MSDataSetGenerator" as suggested by some forums.
2. Also tried clearing the system cache and closing and opening the Visual Studio.
3. Changing the connection strings to different DB servers.

Can anybody suggest me any workarounds/solutions to this issue.

Please give your comments if you need any more inputs on the problem because I am really stuck here

Posted 17-May-12 2:40am

bbirajdar

Updated 17-May-12 20:40pm

v3

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wendelius · Answer 1 · 2012-05-17T02:49:00

Solution 1

I take it you have verified that the schema is actually correct in the XSD. Found this[^] which could be helpful

Posted 17-May-12 2:49am

Wendelius

Updated 17-May-12 2:50am

v2

Comments

bbirajdar 17-May-12 9:20am

Thank you for the reply. However, both the solutions mentioned there did not work for me. Apart from that the command name mentioned there should be "xsd.exe" instead of "xds.exe". The second solution I have tried already