Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We were using class 'System.Xml.Xsl.XslTransform' in our project and now recently we started using resharper. This throw waring Class 'System.Xml.Xsl.XslTransform' is obsolete: “This class has been deprecated. Please use System.Xml.Xsl.XslCompiledTransform instead. http://go.microsoft.com/fwlink/?linkid=14202“
Is it good to update the code to new class or keep the existing as the system performs well.
Is there any disadvantages with this approach.
Warnings are just that – not an error, but something you should be aware of. If the code performs well enough now, feel free to leave it as is. Just know that the API may disappear in the future so you’ll have to deal with it eventually if you upgrade.