*/
.NET Protector + compressor + framework detector 1.965
Submitted By:
jonathanclark
Rating:





(
Rate It)
Thinstall.net protects your .net programs against all forms of
static analysis including byte code, unmanaged code, and
resource data. Thinstall.net is the only protector preventing
disassembly that is backward and forward compatible with all
versions and service packs of .NET. Thinstall.net requires no
external files and usually compresses programs by 50% or more.
Thinstall.net allows full use of reflection and does not mangle
crash traces produced by your program. Thinstall.net will
automatically check for the presence of the .NET framework
before starting your program. If it is missing the user will be
informed and directed to Microsoft's download page via the
locally installed browser rather then displaying the cryptic
message "Missing DLL, MSCOREE.DLL".
File Details
NOTE: Some downloads must be obtained through publishers´s site.
Do you want to get your software listed on this site? Go to our
submissions area.
Screenshot
Details
Number of downloads:
2359
Comments (3)
useless in terms of code protection
Posted on Friday, June 06, 2003
Completely false statement, it does not offer any real protection. Protected .NET apps can be so easily reversed that I think it is totally useless.
"Thinstall.net is the only protector preventing disassembly that is backward and forward compatible with all versions and service packs of .NET"
Excellent Software!




Posted by: Brian Schneeberg on Monday, July 21, 2003
After evaluating the majority of the obfuscators/protectors listed on this site with my 10+ assembly solution (wich uses a fair amount of reflection), Thinstall was the only program able to handle the multiple assemblies without introducing errors. My guess as to why this is the case is because it encapsulates the code versus obfuscating it.
To add to the comment from Anonymous...




Posted on Monday, December 29, 2003
Thinstall can introduce problems into the application that can be obtuse, hard to reproduce, but still fatal for your customers while nearly impossible for the Thinstall's creator to correct.
As a result, you will find that Thinstall either works for your application or doesn't, simple as that. If you product is complex, you may require months of re-testing after the integration of Thinstall.
After months of such effort you may even find Thinstall to be inappropriate for your product. Not exactly the result you'd want to see from months of testing and diagnosis.
My suggestion: recognize the intellectual property protection restrictions inherent to object-oriented, component-oriented, virtual-machine-based platforms such as .NET.
Purchase a solid code obfuscation tool, one that seamlessly handles multi-assembly projects.
For complex applications, ones where Thinstall is more likely to cause problems, obfuscation is as good as it gets.
Add Your Rating