MessageSecurityException

Question

0.00/5 (No votes)

See more:

Hi,

I'd like to develop a WCF service, and a Client.
I'd like to upgrade them also, but without restarting them.
To do this, i've hosted teh service in IIS.
In this way, i can update the service - by changeing the underlying dll -
flawlessly due to IIS hosting, but if a client is connected,
the client will fail after the next
call. Then i receive the MessageSecurityException.
If i restart the client, when the update finished it works fine...
Is there a way, to update them both without restarting them?

thx

collapo

Posted 14-May-10 5:07am

collapo

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Rutvik Dave · Accepted Answer · 2010-06-03T07:57:00

OK. the short answer is 'No, you cannot'.

Now when you compile a WCF service, it will generate .dll, which will be used when hosted on IIS, now remember that .dll will always run inside the process. so it will be executed by the App Pool in IIS, because .dll can not execute on its own. so when you update the .dll it will restart the app pool on IIS.

so what you can do is, handle the exception on client side, and then display an error page with 'connection lost' message (by passing a current page as query string), and a link with 'try again' which will redirect again to that page url, passed on query string.

You are not going to update the WCF service that frequently, so I don't see any problem with this.