Wrox Programmer Forums
|
ASP.NET 1.x and 2.0 Application Design Application design with ASP.NET 1.0, 1.1, and 2.0.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ASP.NET 1.x and 2.0 Application Design section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old September 4th, 2003, 02:37 PM
Authorized User
 
Join Date: Jul 2003
Posts: 13
Thanks: 0
Thanked 0 Times in 0 Posts
Default unable to retrieve cache

I have an application that writes a substantial amount from a DataSet to the Cache using the DataSet.WriteXml(stringwriter) method. On the next page I attempt to perform DataSet.ReadXml() to retrieve the cached information, but I receive the error message "The path is too long after being fully qualified. Make sure path is less than 260 characters." Any ideas why this is happening? Which path is it referring to? Thanks in advance for any help.
 
Old May 16th, 2005, 09:08 AM
nae nae is offline
Registered User
 
Join Date: May 2005
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi burdickdave:

I encountered the same error when returning a dataset from a WebMethod. Code looks loke this:

In the WebMethod:
...
return oDs.GetXml();


In the WebClient:
oDs.ReadXml(MyStringReplyingWebMethod());

Did you find a cure for your problem?
Thanks.

nae





Similar Threads
Thread Thread Starter Forum Replies Last Post
about using cache benordz ASP.NET 2.0 Basics 2 April 25th, 2008 09:19 AM
cache problem benordz C# 5 April 25th, 2008 01:01 AM
Cache problem alton Classic ASP Basics 3 September 6th, 2004 12:37 PM
cache pab006 Classic ASP Basics 3 January 22nd, 2004 05:29 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.