[dll - after Obfuscation] Problem: precompilation needed?

  • Thread starter Thread starter teo
  • Start date Start date
T

teo

After I've obfuscated a precompiled dll,
to protect it,
it works no more.

---- ------ -------

I'm with 'AspNet 2.0' and 'Visual Studio 2005'
and
'Dotfuscator Community Edition' (the poorest)

---- ------ -------

Simple steps:

I precompiled my web app
(only a Button and a e Textbox)
with the Updatable option check 'Off'

I loaded the generated dll
on the Bin folder on the server
it works

---- ------ -------

I decid to protect my web app

I used Dotfuscator (embedded in VS2005)

I loaded the precopiled dll I had
and obfuscted it

It generates a new dll , with a different name

I loaded this obfuscated dll in the
Bin folder on the server

but my web app doesn't work
Message:
"The file 'Default.aspx' has not been pre-compiled,
and cannot be requested"

---- ------ -------

What have I to do in order to have my web app working
or to better say
to protect any web application I develop?

---- ------ -------

Thanks
 
I'm not sure you can obfuscate precompiled assemblies from the use of the
WebSite Project model. Download the Web Application Project add-in, convert
your project to a Web Application project (which will create a single
assembly dll ) and try obfuscating that. But having said that, I would add
that obfuscation isn't much of a deterrent.
Peter
 
I'm not sure you can obfuscate precompiled assemblies from the use of the
WebSite Project model. Download the Web Application Project add-in, convert
your project to a Web Application project (which will create a single
assembly dll ) and try obfuscating that. But having said that, I would add
that obfuscation isn't much of a deterrent.
Peter
Click to expand...

That add-in (and its related updating set of files )
is suitable to an English version of VS2005;
I also read the faq and they confirmed this.

Any Italian version in the meanwhile?
Any workaround?

How can I protect my work ?????
 
Back
Top