Toolbox: Distributed Caching, Object-Object Mapping, Blogs and More

 I'm making the leap to move from vb.net to C#, and I'm getting this crazy error when I try to execute one sp, set a value, and then execute another sp based on the value.   Any suggestions??? proc_GetSectionDetails is my first stored procedure.  From that, I get a value for SectionID, and then use it for the second sp called  proc_GetSectionDetails protected void getSectionContent() { SqlConnection conn = default(SqlConnection); SqlCommand comm = default(SqlCommand); SqlDataReader reader = default(SqlDataReader); string connectionString = ConfigurationManager.ConnectionStrings["123"].ConnectionString; conn = new SqlConnection(connectionString); comm = new SqlCommand(); comm.Connection = conn; comm.CommandType = System.Data.CommandType.StoredProcedure; comm.CommandText = "proc_GetSectionDetails"; comm.Parameters.AddWithValue("SubSectionID", Request.QueryString["SubSectionID"]); conn.Open(); reader = comm.ExecuteReader(); if (reader.Read()) { lblName.Text = Convert.ToString(reader["SubSectionName"]); lblDesc.Text = Convert.ToString(reader["SubSectionDescription"]); Label SubSectionParentID = new Label();

Hi,

I am trying to use the chart object provided in vs 2010. 

Specifically, I am trying to use the chart object to create a web part.

I noticed that the chart object did not appear in the toolbox when I opened it. I found a link that suggested I run an install program to add the chart object in. I now have the chart object appearing in the toolbox, but when I attempt to drag it onto the form I keep getting messages about "Error Creating Control" - Object reference not set to an instance of an object.

Where should I go from here? Is the chart a bit unstable? Do I need to reinstall from elsewhere?

 

Thanks.

 

Hello,

I am using XML in getting client data in 3-tier architecture, using XDocument in passing XML among layers.

But when I use it in inserting this XML in XDocument, it throws the following error:

No mapping exists from object type System.Xml.Linq.XDocument to a known managed provider native type. 

I am using the following code, it throws the exception at the bold line: