Last post Dec 07, 2005 07:52 AM by tearls
Dec 06, 2005 05:09 PM|tearls|LINK
Hello I recently upgraded from v3.1 to v3.2 and when coding I noticed this message
XMLEncode Replaced by DotNetNuke.Common.Utilites.XMLUtils.XMLEncode
Can anyone explain this? The app was built successful, but I still get this message. I have refreshed references, but this message still persists.
The message can be seen when hovering over a XMLEncode line in code behind.
I must be missing something.
Dec 06, 2005 08:12 PM|jbrinkman|LINK
This just means that the function has been deprecated in 3.2 and a similar function is now available using DotNetNuke.Common.Utilities.XMLUtils.XMLencode. While you can continue to use the function for now, you should try to convert all your code to use
the new function. At some unspecified point in the future we may remove the deprecated method.
The warning you get is just a warning that reminds you to update your code. This allows us to keep refactoring and improving the core, and also notify developers of future breaking changes, so that hopefully developers will switch to the new function and
thus prevent future compatability issues.
We are constantly looking at the DNN API and will continue to consolidate and improve the API. Since the API is written in an AD HOC fasion, we often find that some method is placed in a class where it really doesn't belong, or it is in a namespace that
doesn't make sense. Sometimes, we expand whole areas of the API and want to consolidate methods in one place that provide a common set of services. In any case it is a good sign that we are working to constantly improve the developer experience.
Dec 07, 2005 07:52 AM|tearls|LINK
Thanks for the great explanation!
Just one more question. Does this mean we have to convert the code for the core modules ourselves or will this eventuall be completed in a later release?