OK I'm cheating a bit, but I promise not to cross-post again! I posted this to the DiscountASP.net forum, but since it does not get much traffic, and because this question might not be DiscountASP.net related, I'm reposting here. Forgive me,
but I have a sneaky suspicion this might not be as simple as a SSL certificate lacking a private key.
Any ideas what this might be? I'll post any answers I get from DiscountASP.net here, just to complete the record for future reference.
One more thing: I did not use the 'makecert' command, since this is a project where the WCF web service resides not on my localhost machine, but remote, at the DiscountASP servers. They (the DASP people) set up the SSL certificate--I assume they
did so properly. All I did was import it from there, and stored it in the '/My' folder of where I use Visual Studio 2008. In nearly all examples on the net, the tutorials assume you 'self-sign' your certificate with both the server and client residing
locally, in the Visual Studio internal built-in server. This is not the case here. What I'm hoping is that it's a simple problem where the SSL certificate I bought does not include a private key--though it's pretty useless for programming purposes
if it does not. Googling this issue I see there are a few threads on this topic bu
View Complete Post