Best solution to update the applications

Hi

I'm developing a client/server sistem (based on .NET Framework 2.0
(C#) using VS 2005):

1. A webservice
2. A client WinForms application.

Classic.

Now, the client app will be installed in many locations and will
access the webservice.
I want 2 things:

1. The client app and the webservice should be "version compatible".
That means, if the webservice is version 1.5.1.2340 (including the
build number), it should work ONLY with 1.6.2.3456 version of the
client application.

Trying to access the webservice using a different version of client
app should deny the access.

2. Automatically upgrade the client application(s) so there's no need
for another qualified person to install an update. I imagine that the
webservice should provide the update package to the client app, the
client app should download it and install it automatically (this means
even registering COM dll's, etc). After the update process, the
webservice should accept only connections from the client application
having the right (the new) version.

Which format should the package be? Is there a standard scenario for
such operations?

The webservice and the client will communicate through secured VPN, if
this should matter in choosing the right solution.

Thanks.
.

Relevant Pages

  • Re: WSE352 Size of the record exceed its limit
    ... The webservice is a WSE service component soap client. ... you're developing an .net webservice which uses WSE ...
    (microsoft.public.dotnet.framework.webservices)
  • RE: Error on SOAP Call on only one machine: Could not find default endpoint element that references
    ... "Service Reference" is a proxy class used for consuming WCF service. ... Though WCF client can also consume standard XML webservice, ... Microsoft MSDN Online Support Lead ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Webservice problem (after iisreset)
    ... I was speaking about whatever means you're suing the make the call from the client. ... If it already waits one minute for the failure then it sounds like the timeout is already high enough. ... So use wsdl.exe to generate a .NET proxy to your webservice to see if that style of client has the same problems or not. ... If it does, then it sounds like something on the server, if it does not then it's likley your HTC framework. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • RE: WebService returns a custom object
    ... There are many many attributes that control serialization. ... WebService returns a custom object ... WS can expose only the following types as ... > service infrastructure or any commercial tools will provide a client side ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: How does the client of a webservice figure out a complex type
    ... attribute with a hint for the client side proxy this is a DataSet. ... >if the wsdl does not contain any reference, ... >> As for how webservice client figure out a complex type, ...
    (microsoft.public.dotnet.framework.webservices)
Loading