rliq
May 12th, 2009, 09:56 PM
I have a few C# 3.5 Windows Forms Client applications that connect to a few .NET 2.0 Sercure Web Services. All of the code (both ends) belongs to me.
I was running VS2008 on XP...
I recently moved my development environment to Vista. Since that point I have not been able to update any of the Web Services referenced from any of the client applications. If I delete the reference to the web service and re-add I get an error. The error is the same in both cases.
There was an error downloading 'https://[URI].asmx'.
The underlying connection was closed: An unexpected error occurred on a send.
Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly res
Incidentally, I could not open the Web Services in IE8.0 before I changed the IE advanced options to "Use SSL 2.0".
If I specifiy http (with no S) it works fine, but I do not want to do that.
Also, if I compile/run the client application on XP, it works fine, but if I then copy the EXE to Vista, I get the same error as above when I run the application on Vista.
I'm not sure where I should ask this question, but I was hoping someone here may have experienced it too.
I was running VS2008 on XP...
I recently moved my development environment to Vista. Since that point I have not been able to update any of the Web Services referenced from any of the client applications. If I delete the reference to the web service and re-add I get an error. The error is the same in both cases.
There was an error downloading 'https://[URI].asmx'.
The underlying connection was closed: An unexpected error occurred on a send.
Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly res
Incidentally, I could not open the Web Services in IE8.0 before I changed the IE advanced options to "Use SSL 2.0".
If I specifiy http (with no S) it works fine, but I do not want to do that.
Also, if I compile/run the client application on XP, it works fine, but if I then copy the EXE to Vista, I get the same error as above when I run the application on Vista.
I'm not sure where I should ask this question, but I was hoping someone here may have experienced it too.