|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Assembly SecurityForgive my ignorance. :)
I am new to .Net development and I am a little confused as to how assemblies are protected from someone stealing them. I am used to using Delphi to develop Win32 applications and in that arena, nearly everything (controls, components, etc.) are compiled right into the executable. And since third-party controls and libraries were compiled into the executable, it was impossible for someone to steal these expensive controls. What protects someone from stealing third-party assemblies? Let's say I purchase a library and place them in the windows program's bin directory. Can't someone else using the machine simply copy this assembly for their own use? Any help is appreciated, and a link to any information on this subject will be very helpful. >What protects someone from stealing third-party assemblies? Licensing. It doesn't protect from stealing, but from using thecomponent without a license. http://msdn2.microsoft.com/en-us/fe8b1eh9(VS.71).aspx There are also tools to merge multiple assemblies into one that you can use if the component vendor supports it. Mattias -- Mattias Sjögren [C# MVP] mattias @ mvps.org http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com Please reply only to the newsgroup. Thanks, Mattias.
Show quote "Mattias Sjögren" <mattias.dont.want.spam@mvps.org> wrote in message news:%23Btue12RHHA.388@TK2MSFTNGP04.phx.gbl... > >>What protects someone from stealing third-party assemblies? > > Licensing. It doesn't protect from stealing, but from using the > component without a license. > > http://msdn2.microsoft.com/en-us/fe8b1eh9(VS.71).aspx > > There are also tools to merge multiple assemblies into one that you > can use if the component vendor supports it. > > > Mattias > > -- > Mattias Sjögren [C# MVP] mattias @ mvps.org > http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com > Please reply only to the newsgroup. |
|||||||||||||||||||||||