I
believe the error in "There is
no source code available for the current location" belongs to debugging
process related Visual studio.
Thanks
Hanna
-----Original Message-----I tend to agree with some of what you say. I have had a persistent problem, only present when using AjaxPro, that was easy to "work around", however it took me time to figure that out. Thankfully, I found the bug and not a user! I am beginning to wonder if simply using a JSON library and ATLAS to make async calls won't suit 80-90% of what I need from AjaxPro and be a better solution. I really applaud Michael and his efforts, however, I feel like for long term viability, a more active (open source like maybe) community needs to be in place.
From: [email protected] [mailto:[EMAIL PROTECTED]On Behalf Of Jon Ceanfaglione
Sent: Monday, September 11, 2006 3:38 PM
To: [email protected]
Subject: [ajaxpro] Re: Not using AjaxPro anymoreOn 9/11/06, Phuff <[EMAIL PROTECTED]> wrote:
Just to accent a funny issue:
"There is no source code available for the current location"
I get this error now all of a sudden on one of my calls.
??
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ajax.NET Professional" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/ajaxpro
The latest downloads of Ajax.NET Professional can be found at http://www.ajaxpro.info/
Don't forget to read my blog at http://weblogs.asp.net/mschwarz/
-~----------~----~----~----~------~----~------~--~---
