Thanks for the reply. Actually I tried this one but it did not help. I will
see in the config file to make sure I am not making any other mistake. I just
want to ask do I have to change only the section <binarySecurityTokenManager>
or (securityTokenManager> section also). On the blog I have found these two.
I will first try with <binarySecurityTokenManager> and let u know if I it
helps out.
Thanks
KDV
> p.s.
>
[quoted text clipped - 79 lines]
> >>> Thanks
> >>> KDV
it worked for me.
The blog pointer was for more eduction.
Use the code he pasted in the message here.
I put it in my web.config and voila! All was well again. Hooray Pablo.
A warning - put it in your client's app.config, too. That way if the client
app gets deployed to windows xp, it will also know to use rsa15, not it's
default of oaep.
julie
> Thanks for the reply. Actually I tried this one but it did not help. I
> will
[quoted text clipped - 102 lines]
>> >>> Thanks
>> >>> KDV
KDV - 14 Feb 2006 00:18 GMT
Thanks for your help. It worked and I can access service running on Win2000
Pro from WinXP client. The problem I was facing before because I was
accessing the service through DLL. So I changed the configuration in the dll
config and WSE was not finding it. So as long as I use exe.config or
web.config then there is no problem. Is there any way I can tell the client
application to look in dll.config instead of exe.config
Now I have some settings in dll.config and some in exe.config. I want to
make use of app.config which I have included in DLL assembly. ( I think there
may be a way to apply these settings through code, but I don't know how???)
Thanks once again
KDV
> it worked for me.
>
[quoted text clipped - 116 lines]
> >> >>> Thanks
> >> >>> KDV