linqtoxsd Issue Tracker Rss Feed

Closed Task: Overwriting generated files. [4127]

sergey_shandar — Thu, 16 May 2013 10:27:19 GMT

Currently, every time you convert XSD, linqtoxsd overwrites generated C# files, even if the generated files are the same as old ones. It forces Visual Studio to recompile projects which are using the generated files.

linqtoxsd could check old C# file and do not overwrite it if it is the same as new one.

Closed Issue: "bin/Debug" folder for the Build tool. [4128]

sergey_shandar — Thu, 16 May 2013 10:27:19 GMT

I do not know why, on one computer Microsoft.Build compiles everything into "c\bin\Debug". After I've tried on another computer, it compiles to "....XObjects\bin\Debug".

Closed Feature: Signed assemblies [4158]

sergey_shandar — Thu, 16 May 2013 10:27:19 GMT

See http://linqtoxsd.codeplex.com/Thread/View.aspx?ThreadId=204613.

Closed Issue: Element/SimpleType/Union is broken [5600]

sergey_shandar — Thu, 16 May 2013 10:27:18 GMT

<?xml version="1.0" encoding="utf-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="A"
xmlns:A="A">

<xs:element name="account">
<xs:simpleType>
<xs:union memberTypes="xs:string" />
</xs:simpleType>
</xs:element>

<xs:element name="root">
<xs:complexType>
<xs:sequence>
<xs:element ref="A:account"/>
</xs:sequence>
</xs:complexType>
</xs:element>

</xs:schema>

Compilation gives error.

Closed Issue: Attribute/SimpleType/Union is not working. [5609]

sergey_shandar — Thu, 16 May 2013 10:27:17 GMT

Test case:

<?xml version="1.0" encoding="utf-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="A"
xmlns:A="A">

<xs:element name="account">
<xs:complexType>
<xs:attribute ref="A:a"/>
</xs:complexType>
</xs:element>

<xs:attribute name="a">
<xs:simpleType>
<xs:union memberTypes="xs:string" />
</xs:simpleType>
</xs:attribute>

</xs:schema>

Commented Issue: Boolean values are not handled correctly [8676]

RolandasR — Tue, 16 Apr 2013 18:11:32 GMT

Type of boolean values should be lowercased when using toString() method. Uppercase values generate an invalid xml which is not validated against schemas with boolean values. Valid values are: "true", "false", "0", "1".

At least it fails when using boolean simple type list.
Comments: ** Comment from web user: RolandasR **

The buggy code is in SimpleTypeValidator.cs file, class ListSimpleTypeValidator, method:
```
internal static string ToString(object value) {
Debug.Assert(value is IEnumerable);
IEnumerable list = (IEnumerable)value;
StringBuilder bldr = new StringBuilder();

foreach (object o in list) {
// Separate values by single space character
if (bldr.Length != 0)
bldr.Append(' ');

bldr.Append(o.ToString()); // <-- bad things happen here
}
return bldr.ToString();
}
```

Commented Issue: Boolean values are not handled correctly [8676]

RolandasR — Tue, 16 Apr 2013 17:48:29 GMT

Clearing the issue a bit. All simple type lists use toString() method in XObjects class when saving final Value for XElement. Almost all simple lists do a bad thing when new values are added. An example of such schema:
```
<xs:simpleType name="bitList">
<xs:list itemType="bit" />
</xs:simpleType>
<xs:simpleType name="bit">
<xs:restriction base="xs:boolean" />
</xs:simpleType>
```
The same happens with all dates/times as well. As a workaround, one could use rootElement.Untyped.SetValue() method to fix an issue.

Created Issue: Boolean values are not handled correctly [8676]

RolandasR — Fri, 12 Apr 2013 14:53:02 GMT

Commented Issue: How to obtain the Value of an element of complexType where mixed="true" [2047]

unfug_rockz — Wed, 29 Aug 2012 13:27:00 GMT

I am using LINQ-to-XSD to process XML elements named "labl", defined in the schema as follows:

<xs:complexType name="lablType" mixed="true">
...[definitions of optional elements and attributes]...
</xs:complexType>

My actual XML file looks like this:

<labl>
The text of the label
</labl>

where <labl /> is defined in the schema as being of type "lablType". My current C# code using LINQ-to-XSD looks like this:

var lablNodes = from children in rootNode.Load("fileName").childNode
from labls in children.labl
select labls;

foreach (lablType labl in lablNodes)
{
string label = ((XElement)labl).Value.Trim();
}

In other words, I am having to revert to untyped LINQ-to-XML to get the actual text of the <labl /> node, because the automatically generated class "lablType" does not seem to include a property for the text, only the attributes.

Is there a way to do this using typed variables/LINQ-to-XSD? Am I missing something simple?

Thanks in advance,

Ed Graham
Comments: ** Comment from web user: unfug_rockz **

Same Problem here.
mixed="true" not working

Is there an working alternative to linqtoxsd?

Commented Issue: Build project broken [7638]

sr_codeplex — Wed, 04 Jul 2012 21:16:35 GMT

The Build application uses .svn\entries file to obtain revision information directly from the SVN "entries" file. However, the SVN working copy metadata format recently changed and the build project is now broken.

I worked around the problem by changing the Revision() function as follows:
static string Revision()
{
using (var reader = new IO.StreamReader("../../../../.svn/entries"))
{
return reader.ReadLine();
}
}
Note that I an not sure what the first line of the entry files contains, just that it returns "12" for me (which allows the build to proceed). Perhaps this dependency can somehow be removed to prevent issues like this in the future?
Comments: ** Comment from web user: sr_codeplex **

I hope not. cheer :P

Commented Issue: Build project broken [7638]

manchuwook — Wed, 04 Jul 2012 20:38:21 GMT

Did the developer on this project die or something?

Commented Issue: Illegal characters in path. [6282]

chiragbhagat — Thu, 28 Jun 2012 16:27:31 GMT

I've been trying all day to get Linq to Xsd to work. But all I receive is "Illegal characters in path." message.

The error seems to appear when using $(ProjectDir) and $(SolutionDir) so I tried using C:\LinqToXsd. Which allowed me to reload project successfully.

But when trying to build i get error:
C:\LinqToXsd\LinqToXsd.targets(29,5): error MSB6001: Invalid command line switch for "LinqToXsd.exe". Illegal characters in path.

I've even tried to change all references in LinqToXsd.targets to use C:\LinqToXsd without success.

Please help me, I would really like to use this
Comments: ** Comment from web user: chiragbhagat **

I had the same issue. I ran the command manually several times and found that output path should not end with "\" character (parameter -o:<path>). I removed last slash and it worked for me.

Created Issue: Build project broken [7638]

djbuijs — Tue, 17 Jan 2012 13:57:44 GMT

Created Issue: Build project broken [7637]

djbuijs — Tue, 17 Jan 2012 13:57:39 GMT

Commented Issue: How to obtain the Value of an element of complexType where mixed="true" [2047]

robbie_hinch — Thu, 13 Oct 2011 14:09:38 GMT

I have just bumped into the same problem and can't find much info about how to get round it

Commented Issue: LinqToXsd.targets does not support multiple XSD's in same project [6305]

owangen — Thu, 08 Sep 2011 13:16:06 GMT

If you have multiple XSD's in one project and one to use LINQ to XSD on all of them you will get an build error: 'The item obj\... was specified more than once in the "Sources" parameter. Duplicate items are not supported by the "Sources" parameter'.

The fix is quite easy. Just replace "LinqToXsdSource.cs" in the LinqToXsd.targets to "LinqToXsdSource_%(LinqToXsdSchema.Filename).cs". This will generate unique names for each XSD (As long as they don't appear twice with the same name in the project).
Comments: ** Comment from web user: owangen **

If you have multiple XSD's which do imports from common XSD's this will not work...

Commented Issue: Can not debug(breakpoint did not hit) IEnumerable IXTyped.Descendants() [6814]

JVennix — Tue, 16 Aug 2011 16:56:43 GMT

How can i debug code in namespace API such as....XObjectsQueryExtension.cs i've been trying to fix bug but it 's always pass through breakpoint ...wanna help!?
Comments: ** Comment from web user: JVennix **

Deploy the pdb together with the debug DLL. That should fix it.

Created Issue: Can not debug(breakpoint did not hit) IEnumerable IXTyped.Descendants() [6814]

sr_codeplex — Tue, 14 Jun 2011 12:09:50 GMT

How can i debug code in namespace API such as....XObjectsQueryExtension.cs i've been trying to fix bug but it 's always pass through breakpoint ...wanna help!?

Created Issue: Bug Query.Descendant [6812]

sr_codeplex — Tue, 14 Jun 2011 08:01:59 GMT

Could you please fix this http://linqtoedmx.codeplex.com/SourceControl/changeset/changes/32344

thanks in advance ^^.

Created Issue: Bug Query.Descendant [6811]

sr_codeplex — Tue, 14 Jun 2011 08:00:42 GMT

Could you please fix this http://linqtoedmx.codeplex.com/SourceControl/changeset/changes/32344

thanks in advance ^^.