I just found a solution: 1. Open the project in XACT 3. 2. Switch to Streaming mode. 3. Save the project. 4. Switch back to In Memory mode. 5. Save again 6. It will work.

Thank you guys for replies.

[quote user="Stephen Styrchak"][quote user="Mahdi Khodadadi Fard"]It is not a native dll, but a .net assembly and needs .net framework to run. protected assemblies even run on WinCE (with some corrections by hand) and i am completely sure it is not native (at least i have read The Common Language Infrastructure Annotated ...

[quote user="Shawn Hargreaves"] Sure, this will require an attacker to do a little more work before they can load the code into Reflector, but this isn't exactly a hard problem for any remotely experienced hacker to solve. The only 100% sure way to protect your code is through the legal system. There is no such thing as a ...

[quote user="Stephen Styrchak"] I looked up the CodeVeil tool he used as an example. The reason Reflector says the assembly doesn't have a valid CLI header is because it doesn't - it is actually a native image! The tool creates a native application with the MSIL assembly embedded as an encrypted resource. When executed, the ...

[quote user="Stephen Styrchak"]Could you please clarify what you mean when you say you want to "protect" your MSIL code, but not obfuscate it?[/quote] Obfuscated (Human unreadable) code can be converted to readable code by tons of tools. however, even if the code is not readable one can modify it using say, Reflector's ...

Stephan, Your solution didn't work. as i wrote in my first post Dotfuscator didnt work. However, if it worked the result is not what i expect. i need to protect MSIL code not to obfuscate it. There are lots of decompilers that detect obfuscation algorithms and generate compilable source code. also lot of tools that allow you to directly ...

Thanks George. To Aeon: 0, 1, 2, ... files: one one them is the .dll, rename them one by one to .dll and then open them in Reflector. Anyway thanks for replies.

Jim Perry: Because i want to publish my .dll, but i want to protect the source code from unwanted eyes. Aeon: Even if my project is not a single .dll, it is easy to unzip a .ccgame file and file the executable and of cource the source code. Thanks for replies.

Hi, I want to protect my assemblies, but i receive error code 3 in xbox (there is no problem in Windows) I have used this tools: Dotfuscator. Xenocode Post Build. DeployX Codeveil. Can anyone show me a tool or a solution to protect the assemblies ? Thanks in adv.