'wrapExternalObect' .net 9.1.0.1 in vb.net.
Added by Anonymous almost 16 years ago
Legacy ID: #5798771 Legacy Poster: pvallone (pvallone)
Hi, I am using Saxon .net 9.1.0.1 in vb.net. I get this error when trying to create a wrapper for a .net extension: 'wrapExternalObject' is ambiguous because multiple kinds of members with this name exist in class 'Saxon.Api.XdmAtomicValue'. code: transformer.SetParameter(New QName("", "timezone"), Saxon.Api.XdmAtomicValue.WrapExternalObject(TimeZone.CurrentTimeZone)) After reading this error on the MSDN site: The most likely cause of this error is case sensitivity. Visual Basic names are case-insensitive, which means you can capitalize them differently at different places in your code. For example, if you define a variable with the name XYZ and later access it as xyz, the compiler considers the two names to be equivalent http://msdn.microsoft.com/en-us/library/ms235408.aspx Not sure if this is a "bug" for just a compatibility issue. Thanks.
Replies (2)
RE: 'wrapExternalObect' .net 9.1.0.1 in vb.net. - Added by Anonymous almost 16 years ago
Legacy ID: #5798929 Legacy Poster: Michael Kay (mhkay)
Ouch. The method exists (synonymously) as both wrapExternalObject() and WrapExternalObject(), which I did because I accidentally made it lower-case in the first release, and I thought having both methods was the best way of fixing that without causing backwards compatibility problems. I'm not sure what to do about it now: I think I'll have to bit the bullet and drop the one that starts with lower-case, and anyone affected will just have to change. Next decision is whether to do this in a maintenance release or wait till 9.2. I'm inclined to wait.
RE: 'wrapExternalObect' .net 9.1.0.1 in vb.net. - Added by Anonymous almost 16 years ago
Legacy ID: #5799000 Legacy Poster: pvallone (pvallone)
Hi Michael, No worries, I can wait (or build the project in C#). Thanks for the fast reply. Phil
Please register to reply