We are in the process of upgrading our existing behavior calls
(webservice.htc) to the more 'supported', as they say, concept of
AJAX. One thing I noticed was that the .htc code practically does the
same thing AJAX does - with nice code that allows you to .value
reference the return XML nice and easily - and now I'm wondering why I
should even bother trying to reinvent the wheel.
The one thing I noticed so far that really looked like an issue is
that the .htc file uses the older 'Microsoft.XMLHttp' object. As far
as I know, there are newer versions (and I'm guesing faster as well)
such as 'MSXML2.XMLHttp.5.0'. I tried to hack the code to instantiate
the 5.0 object and it blew up. I am assuming this is due to the fact
that webservice.htx is not backwards compatible and/or hardcoded
specifically for the 'Microsoft.XMLHttp' object.
Has anyone come across this situation? Is there much to gain by moving
from 'Microsoft.XMLHttp' to 'MSXML2.XMLHttp' object? Should I just
keep the webservice.htc and continue using it, or is it worth to dive
in and upgrade to the newer AJAX stuff?
Thanks for your thoughts...
"ChrisHarrington" wrote:
I'm not sure that webservice.htc was ever supported. But I still use it
(probably with some minor modifications) with .net 2.0
"Ulf" <Ul*@discussions.microsoft.comwrote in message
news:01**********************************@microsof t.com...
I have found Ajax and webservice.htc that is not supported any more.
Is there a built in funcion for webservices in Visual Studion 2005 / .Net
2.0 ?
What is the best solution ?
