Where is Microsoft.Practices.Unity.dll?

I'm trying to obfuscate and merge my application. I've been able to merge and obfuscate all the dlls that are not Microsoft.Practices.*.dll.

But I can't merge or obfuscate (in any order) the remaining dlls, because I keep getting an error that the Microsoft.Practices.Unity assembly cannot be resolved.

So, where is this assembly?

In the Nettiers templates, there is a references folder.  All the Entlib v4 dll's are in a directory in there.

jeff

Why do you wanto to obfuscate theEntLib dll's?? They're already open source anyways...

Indeed, there it is. Thank you!

I'll try it with the Unity assembly and let you know how things go.

Actually, this project is used like a third-party assembly in unrelated solutions and projects. For ease of deployment, I need to merge all the assemblies referenced by this project into the primary output. For security reasons, I need to obfuscate it since this is a sensitive assembly.

I haven't played with it enough yet, but I think it makes much more sense and is probably much easier to merge everything first and then obfuscate, rather than selectively obfuscate only some assemblies before merging all of them.

If you have any ideas or feedback on this, I'm all e-ears. As it is, I'm learning this stuff on the fly.

Hello,

Why don't you just save your self some time and use ILMerge?

"ILMerge is a utility that can be used to merge multiple .NET assemblies into a single assembly."

Thanks

-Blake Niemyjski

Hi blake05,

Actually, I am using ILMerge, but it only merges and does not obfuscate. In fact, I have to use both, because the Community Edition of Dotfuscator does not support merging.

Anyway, when I use ILMerge, on all the DLLs in the bin\debug folder, or even just on all the Microsoft.*.dll files, it fails because it's missing the Unity assembly.

Now that I know where the Unity assembly is, I can try again. Just haven't gotten around to it yet.

I am curious if other obfuscation tools (open-source or otherwise available for free) are easier to use than Dotfuscator and can be integrated in a build process, but I guess that's a subject for a different thread.