C# packer

[Muji-FightR]

Sorry this is not related to trainers but i'm in need of a packer for C# coded .exe files...
i tried ASPack 2.11 but it just produces crap...
UXPacker also won't work !
Any help is appreciated !
muji !

[caki]

Try CEXE. Its **** when it comes to protecting, but for compression its cool enough. You can find it at:

www.protools.anticrack.de

[Muji-FightR]

THX dude for your response!
But the website you told me wants to have a login name and password
Isn't it public ?

[Quall999]

The creator's site:
http://www.scottlu.com/Content/Projects.html

[Muji-FightR]

It doesn't even start !
I downloaded it from that link but it won't open !
So i ran it in a Win95 compatible mode ("Kompatibitätsmodus" in German) and it finally starts but it sais not compatible with Win98 & 95 ???!!!
I made it Win2000 compatible but it doesn't start !
What shall i do ?

i tried plenty of packers (ASPack, UXPacker, Petite, 20to4, ...) but none of them works...
Petite said "Cannot pack this exe file", ASPack has packed it but the result was a damaged .exe fiel which didn't work...
Please help me !

muJi

[caki]

Ehh man, try dling from somewhere else, cuz cexe works fine for me. I'd upload it somewhere for ya but im not at home right now

[Muji-FightR]

The question is: Does it also work with c# files ?
It will probably work for C, C++, VB, ... but i don't know if it will compress C# coded exe files... ?

[DABhand]

What you fail to realise is this.


No matter what language a program file was before, it is compiled into machine code the computer understands.

So any packing/wrapper will work.

You may have used the wrong syntax to pack the file.

[caki]

Actually DABhand,

With C# and VB.net files the code is compiled into Microsoft Intermediate Language. Then, once you run the exe a Just in Time compiler will compile the
Microsoft Intermediate Language code into native code and then execute it. Also, I think that the Just In Time compiler also checks the PE header to see if it has been changed, because if you change the PE header, the exe wont run. Since most exe packers change the PE header, the exe will not be able to run because the JIT detects these changes and wont run. CEXE packed exes, however, when unpacked do not have any changes in the PE header, thereby allowing the packed VB.net exe or C# exe to run.

[Muji-FightR]

With C# and VB.net files the code is compiled into Microsoft Intermediate Language. Then, once you run the exe a Just in Time compiler will compile the Microsoft Intermediate Language code into native code and then execute it

That's why I asked for a special c# packer...Because it is "precompiled" and has to be compiled by a Just-In-Time compiler ("Jitter") it cannot be packed like normal exe files
The jitter will probably not compile a strange exe file without a valid pe header !
My problem is CEXE doesn't work for me
It won't start with my winXP and in Win95 combatible mode it will, but there is the little sentence "does not work with Windows 95 & 98" ??!!
What shall I do? Is there another packer that works for C# files ?

[caki]

Yeah, there is if you wanna pay 300$

[DABhand]

Originally Posted by rendari

Actually DABhand,

With C# and VB.net files the code is compiled into Microsoft Intermediate Language. Then, once you run the exe a Just in Time compiler will compile the
Microsoft Intermediate Language code into native code and then execute it. Also, I think that the Just In Time compiler also checks the PE header to see if it has been changed, because if you change the PE header, the exe wont run. Since most exe packers change the PE header, the exe will not be able to run because the JIT detects these changes and wont run. CEXE packed exes, however, when unpacked do not have any changes in the PE header, thereby allowing the packed VB.net exe or C# exe to run.

The exe will call on API's that is used via either C# or VB.net. Unless they were stated to be included with the exe, which they never do to reduce sizes.

Hence why most c# or VB proggies require runtime files etc to make em work.

But the initial exe is encoded to a general language that the comp understands.

The only reason that Muji is having problems is that possibly the compiler, wrapped the exe for him already.

[Muji-FightR]

Originally Posted by DABhand

The only reason that Muji is having problems is that possibly the compiler, wrapped the exe for him already.

At first i want to thank you guys for your support and feedback !
@DABHand:
Does this mean the file is already packed while compiling ? I get a result of 200kb merged to 90 kb with ASPack ?! That's why i thought it could be packed again (it finally didn't start but hey, it was a 60% smaller :/ )...

[caki]

I think that the Jitter is acting as a wrapper in this case, preventing muji from packing the file. Thats why I suggested cexe. I have used it in the past to compress vb.net exes. Cexe decompresses the exe onto the hard drive and then runs it, making no changes to the intial exe, while other packers change the PE header, making the Jitter not want to run due to an invalid checksum, crc, or whatever on the PE header.

BTW muji, try dling cexe from here:
http://protools.cjb.net/

I dled from there and packed a custom c# prog I made. It worked fine, so it should also work for you.

[cdkiller]

i suggest UPack v0.30 it got a very high compression ratio.
http://dwing.go.nease.net/

easy to unpack but you asked for a good compression ratio for pe files