While protecting the data is a very good suggestion, I would like to find out
how I can protect my server. This will be win app that will access a remote
server, which in turn has a direct access to database. My concern is that
"Michael Nemtsev" wrote:
> Hello Lelic,
>
> L> have been tasked to convert a VB6 app to c#. The app has a thick VB
> L> client and communicates via internet with database. At the first
> L> glance I was going down the path of Remoting for communication, but
>
> Remoting over what? SOAP, binary? Why did u choose remoting?
>
> L> than I have read couple of post about how easy it is to reverse
> L> engineer the .NET code. I'm concerned that now my Remote server
> L> component's interface and location will be exposed.
> L> The data is highly sensitive, so I'm looking for a suggestion on how to
> protect
> L> compiled code from reverse engineering. Any suggestions are
> L> appreciated.
> L>
>
> sure, but nothing is perfect. What kinda info u wanna protect? just code?
> mb look at protection of your data, not code?
> ..net gives u standart CryptoAPI. u can start from it.
>
> ---
> WBR,
> Michael Nemtsev
> blog:
http://spaces.msn.com/members/laflour >
> "At times one remains faithful to a cause only because its opponents do not
> cease to be insipid. (c) Friedrich Nietzsche"
>
>
>