Re: strong name and web service
From: Guogang (nospam@no_such_domain.com)
From: "Guogang" <nospam@no_such_domain.com> Date: Tue, 8 Apr 2003 18:55:48 -0700
Great, that solves one question, strong name won't be checked by clients.
I am investigating the use of strong naming in our .Net solutions.
Does it make sense to use strong naming on .Net application that won't be
put into Global Assembly Cache?
What can I benefit from strong naming a web service?
"Steven Grayson [MSFT]" <email@example.com> wrote in message
> You can assign a strong name to assemblies that make up a web service, but
> not to a web service. A strong name consists of an assembly's identity -
> simple text name, version number, and culture information (if provided) -
> plus a public key and a digital signature. It is generated from an
> file (the file that contains the assembly manifest, which in turn contains
> the names and hashes of all the files that make up the assembly), using
> corresponding private key. Microsoft® Visual Studio® .NET and other
> development tools provided in the .NET Framework SDK can assign strong
> to an assembly.
> What were you wanting to do by assigning a strong name to a web service?
> This posting is provided "AS IS" with no warranties, and confers no
> Use of included script samples are subject to the terms specified at
> "Guogang" <nospam@no_such_domain.com> wrote in message
> > I saw that I can assign a strong name to my web-service.
> > My question:
> > Is there benefit in assigning a strong name to web service?
> > Will this strong name be checked by any remote client?
> > Thanks,
> > Guogang