.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
 
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!



Home >> Articles >> LINQ >> Post New Resource Bookmark and Share

 Subscribe to Articles

Catching Parsing Exceptions : LINQ to XML Part 5

Posted By :Dhananjay Kumar      Posted Date :07/03/2010   Points :25   Category: LINQ    URL: http://www.dhananjaykumar.net

This is a very high level article which will explain how to handle exception in parsing XML using LINQ to XML.
 


Objective

This is a very high level article which will explain; how to handle exception in parsing XML using LINQ to XML.

Problem

Let us say, we are parsing a below string using XElement.Parse


String strParse = "<Address><Name>Dhananjay Kumar </Name> ";
This string is not valid formed. But XElement.Parse won't be able to catch the exception.  So if we will run the below code

String strParse = "<Address><Name>Dhananjay Kumar </Name> ";
XElement xmlTree = XElement.Parse(strParse);
Console.WriteLine(xmlTree);

We will get the below run time error. 

1.gif

Five Facts 
  1. LINQ to XML is implemented through XMLReader.
  2. Parse methods on various LINQ to XML class are unable to handle the Exception.
  3. At time of parsing if input is invalid XML or not formed exception occurs.
  4. At Exception the underlying XMLReader will throw the Exception.
  5. High level Exception would be System.Xml.XmlException
How to handle the Exception?

Programmer has to explicitly handle the Exception while parsing.  Parsing code need to be put in try catch and Exception must be handled explicitly. 

try
{
  String strParse = "<Address><Name>Dhananjay Kumar </Name> ";
  XElement xmlTree = XElement.Parse(strParse);
  Console.WriteLine(xmlTree);
}
catch (System.Xml.XmlException e)
{
  Console.WriteLine(e.Message);
}

Output

2.gif

Conclusion

In this article, I showed how to handle exception in parsing XML using LINQ to XML. Thanks for reading.


Featured Articles


Best Practices No 5: - Detecting .NET application memory leaks
Memory leaks in .NET application have always being programmer's nightmare. Memory leaks are biggest problems when it comes to production servers. Productions servers normally need to run with least down time. Memory leaks grow slowly and after sometime they bring down the server by consuming huge chunks of memory. Maximum time people reboot the system, make it work temporarily and send a sorry note to the customer for the downtime. ... Read More
.NET Best Practice No: 1:- Detecting High Memory consuming functions in .NET code
One of the important factors for performance degradation in .NET code is memory consumption. Many developers just concentrate on execution time to determine performance bottle necks in a .NET application. Only measuring execution time does not clearly give idea of where the performance issue resides. Ok, said and done one of the biggest task is to understand which function, assembly or class has consumed how much memory. In this tutorial we will see how we can find which functions consume how much memory. This article discusses the best practices involved using CLR profiler for studying memory allocation.... Read More
How to improve your LINQ query performance by 5 X times ?
LINQ has been criticized by many early adopters for its performance issues. Well if you are just going to drag and drop using DBML code generator I am sure you will land up in to mess. Try doing this make a simple LINQ to SQL project using DBML and see your SQL profiler, I am sure you will never like to touch DBML code generator again. ... Read More
Responses

No response found. Be the first to respond this post

Post Comment
You must Sign In To post reply
Find More Articles on C#, ASP.Net, Vb.Net, SQL Server and more Here

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend