What i mean is how can we avoid a 'rogue' component calling a genuine component, or the other way round.
--- Steve Johnson <[EMAIL PROTECTED]> wrote: > Chak wrote: > > > Is there any 'cookbook recipe' on how to protect > the > > components of a .NET application from hacking ? I > have > > heard of the "StrongNameIdentity" attribute, but > would > > like an example, if any. > > What do you mean by "hacking"? What, exactly, would > you like to > prevent? > > -- > Steve Johnson > > =================================== > This list is hosted by DevelopMentor� > http://www.develop.com > Some .NET courses you may be interested in: > > NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles > http://www.develop.com/courses/gaspdotnetls > > View archives and manage your subscription(s) at > http://discuss.develop.com > __________________________________ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
