>code with tools like salamangar. In fact, the salamagar tool even goes as
>names etc etc.
>The O.W.C. Black Book with .NET
>news:%23ysctcWvGHA.5084@TK2MSFTNGP04.phx.gbl...
Quote:
>>Alvin:
>>Compiled dlls have MSIL code but not the real source code. Right?
>>>
>>I'm seeing the source code - comments and all. Why would a dll need the
>>source code?
>>>
>>T
>>>
>>"Alvin Bruney [MVP]" <www.lulu.com/owcwrote in message
>>news:OYXcQXOvGHA.3964@TK2MSFTNGP04.phx.gbl...
>>>The code would compile to a separate
>>>dll and could not be viewed when used in a vs.net project.
>>>Not sure what you mean here, if the dll is available to the client, the
>>>source code is wide open for viewing purposes. Wide open. About the
>>>best you can do is obfuscate it and that will make it a bit more
>>>difficult to decompile.
>>>>
>>>--
>>>________________________
>>>Warm regards,
>>>Alvin Bruney [MVP ASP.NET]
>>>>
>>>[Shameless Author plug]
>>>Professional VSTO.NET - Wrox/Wiley
>>>The O.W.C. Black Book with .NET
>>>
www.lulu.com/owc, Amazon
>>>Blog:
http://www.msmvps.com/blogs/alvin
>>>-------------------------------------------------------
>>>>
>>>>
>>>"Tina" <TinaMSeaburn@nospamexcite.comwrote in message
>>>news:%23W6evaNvGHA.1808@TK2MSFTNGP06.phx.gbl. ..
>>>>In 1.1 I used to use a WebControlLibrary to hold code I didn't want to
>>>>expose when I distributed a component. The code would compile to a
>>>>separate dll and could not be viewed when used in a vs.net project.
>>>>That worked fine and I assume it will still work fine in 2.0.
>>>>>
>>>>However, in 2.0 I tried to use a simple Class library project that
>>>>also compiles to a separate dll. However when I distribute the dll,
>>>>the source code is still visible when debugging in vs.net. Am I doing
>>>>something wrong here or do class library dlls contain source code?
>>>>>
>>>>To do what I want to do should I continue to use the WebControlLibrary
>>>>in 2.0 or is there a better alternative.
>>>>>
>>>>Thanks,
>>>>>
>>>>T
>>>>>
>>>>
>>>>
>>>
>>>
