codegen:nullValue vs msprop:nullValue
- by Ken
Ok, I have datasets that I created way back in 1.1 framework to which we used
codegen:nullValue
within the XSD to handle null values. However if I open one of these datasets with vs 2005 (i.e. 2.0 framework) and add a column, it removes the codegen setting from the entire xsd but adds in
msprop:nullValue
However, unlike previous years, I noticed this time the proper property code was NOT over riden from returning the null value specified in codegen as it was doing in the past. Meaning the msprop appears to be creating the proper code behind the scenes (See example).
Anyone know of any other differnces? Should I be concerned with deploying a new xsd, WITHOUT the codegen code but instead with the msprop xml?
Example:
Original
creates
_
Public Property ParentID() As Integer
Get
If Me.IsParentIDNull Then
Return -1
Else
Return CType(Me(Me.tableCompany.ParentIDColumn),Integer)
End If
End Get
Set
Me(Me.tableCompany.ParentIDColumn) = value
End Set
End Property
New
creates
_
Public Property ParentID() As Integer
Get
If Me.IsParentIDNull Then
Return -1
Else
Return CType(Me(Me.tableCompany.ParentIDColumn),Integer)
End If
End Get
Set
Me(Me.tableCompany.ParentIDColumn) = value
End Set
End Property
BUT is there anything else that might be occuring that I am NOT seeing thus MAKING me re-enter all the codegen settings?
THANKS!
