I'm new to ASP.NET. What are the file extensions that the compiled code
behind is stored in? Are you referring to ASP.NET or VB.NET code when you
say compiled?
When you say library, are you referring to say a VB.NET DLL that the aspx
pages create an object for?
Can you elaborate on this a little more: "then you can use one of several
JIT obfuscator to make reverse engeneering harder." Would this have any
performance hit?
Thanks,
Brett
"Michel de Becdelièvre" <> wrote in message
news:%...
> How about putting the business logic in the compiled code behind ? Or
> better in a library called by code behind or aspx ?
>
> then you can use one of several JIT obfuscator to make reverse engeneering
> harder.
>
> The whole point of aspx is that it is compiled "at first call".
>
> "Brett" <> a écrit dans le message de news:
> ...
>> Say I develop an application that has an SQL Server 2000 back end with
>> ASP.NET front end. All the business logic is in the aspx pages. I want
>> to sell this as a package that some one can install on their server or
>> even desktop (replace SQL Server with MSDE). I don't want people reverse
>> engineering the logic inside of the aspx pages. Is there a way to
>> prevent this?
>>
>> Also, I could probably put most all of the logic inside of a VB.NET EXE.
>> There would still need to be some logic in the aspx pages so I can't
>> completely get away from it. Any suggestions on a good method for this?
>>
>> Thanks,
>> Brett
>>
>
>