Omer van Kloeten's .NET Zen

Programming is life, the rest is mere details


Note: This blog has moved to

Omer van Kloeten's Facebook profile

Omer has been professionally developing applications over the past 8 years, both at the IDF’s IT corps and later at the Sela Technology Center, but has had the programming bug ever since he can remember himself.
As a senior developer at NuConomy, a leading web analytics and advertising startup, he leads a wide range of technologies for its flagship products.

Get Firefox

powered by Dapper 

.NET Resources

Articles :: CodeDom

Articles :: nGineer



References In Visual Studio.NET

Hey, everyone! It's the "Omer Asks For A Feature" time again! ;)

This time, it's regarding a project's references list (in addition to my previous copy/move reqeust):

  1. "Remove Unused References" - You could right click the project, click on this and get all the references your project isn't really using deleted from it. This way, if you're not using any of the pre-supplied references (System, System.Data, System.Xml, etc.), they would get removed so your assembly will not depand on them.
    By the way, the catch is not in finding out which assemblies you use, but on remembering to check which assemblies the references refer to. :)
  2. Conditional References - I can compile my project with conditional symbols so that they affect what gets compiled in my code. I want to be able to specify the symbols required for a reference to actually get into the manifest.
    Why do I need this? Imagine me having my test cases in my main assembly. I can use conditionals to remove the unit testing code so that it's not in my released assembly (#if DEBUG), but I can't remove the reference to the testing framework's assemblies. Yes, JIT will not try to load the referenced assembly, because there's no code referring to it, but then again, it's garbage in my assembly's manifest.

Posted: Jul 16 2004, 05:12 PM by Omer van Kloeten | with 2 comment(s)
Filed under:


No Comments