May 16, 2012 at 8:12 AM
Edited May 16, 2012 at 8:33 AM
|
Hi,
there is no setter generated in below xml tag :(
I used version 3.5.1.0. Now I change to an older version, where it works well.
Is this a change of behavior or is it a bug?
<xs:element
name="MailDir" type="xs:string"
maxOccurs="unbounded"/> is generated as:
Beta 3.5 release 3.5.1.0 (Fev 2012)
[System.Xml.Serialization.XmlElementAttribute("MailDir", Order=8)]
public ObservableCollection<string> MailDir {
get {
if ((this.mailDirField ==
null)) {
this.mailDirField = new ObservableCollection<string>();
}
return this.mailDirField;
}
}
Older 3.4 version generated code:
[System.Xml.Serialization.XmlElementAttribute("MailDir", Order = 8)]
public ObservableCollection<string> MailDir
{
get
{
if ((this.mailDirField ==
null))
{
this.mailDirField = new ObservableCollection<string>();
}
return this.mailDirField;
}
set
{
if ((this.mailDirField !=
null))
{
if ((mailDirField.Equals(value) !=
true))
{
this.mailDirField = value;
this.OnPropertyChanged("MailDir");
}
}
else
{
this.mailDirField = value;
this.OnPropertyChanged("MailDir");
}
}
}
Greetings
Jan
|
|
Coordinator
Jun 10, 2012 at 11:49 AM
|
Thank you to have reported this issue. I have changed code to fix it in branch 3.5 beta.
|
|
|
|
Still seeing the read only behavior in the beta 3.5.1.0.....
|
|
Coordinator
Jul 22, 2012 at 9:42 AM
|
This bug is fixed and a new release has been published (3.5.2.0).
Thank you another time to have reported this bug.
Pascal.
|
|
|
|
pcabanel wrote:
This bug is fixed and a new release has been published (3.5.2.0).
Thank you another time to have reported this bug.
Pascal.
Thank YOU for the great tool :)
I will try it after my holiday.
Greets
Jan
|
|