assemblies

If two assemblies both define namespace A containing class A1 , then the two classes are considered unique types. a) Are the two namespaces also considered unique? b) If program P has a reference to both assemblies, how do we create an instances of the two types? Namely, I keep getting an error when I try to create an instance of A.A1 using A; namespace ConsoleApplication1 { class Program { static void Main(string[] args) { A1 a = new A1(); // error } } } c) But if program P also defines type B.A1 , then compiler doesn’t complain when I declare an instance of A1 : using A; namespace

Is there a way to load a .NET Assembly into a Sandbox environment that is also restricted in custom ways? I know you can run an Assembly in a different AppDomain, but can you limit it from being able to do certain things that you want to restrict? For example: I want to be able to load up a Plugin (simple, just defined via a specific interface) within a separate Assembly within an ASP.NET application, but I only want the plugin to be able to access certain Data Access Layer component and not be able to connect to any databases directly. I'm thinking about the scenario of having a single

In a .net application I am writing, I need to locally cache assemblies from various locations so my application can use them even if the original locations are unavailable. I cannot use the GAC (primarily because I want portability and also because the assemblies might not be signed). Does anyone know of any .net code which supports this functionality already? I need the cache to be able to tell me if a particular assembly is already in the cache and handle different versions of assemblies as well. It is likely that I will have to resort to writing my own assembly cache, but I thought I would

In the past years I've occasionally been wondering what equivalent of the (in)famous DLL_PROCESS_ATTACH was available in the .NET world. Any documentation I have says, slightly simplified, that the earliest entry point to a class is the static constructor (cctor), but you cannot influence when it is called , nor can you define one cctor that's guaranteed to be called prior to any other cctor or field initializer, hack, it may not even be called at all if the class is never used. So, if you want to guarantee something's initialized before any method of your assembly is called and you don't want

If I compile a C# project twice, I will get two assemblies. These assemblies aren't exactly the same (using a binary diff). I can think of reasons why this is so, but the fact remains that the source for the two assemblies are identical. I am concerned with creating a patch between these assemblies, and applying the patch on a customer machine. Does anyone know of a library (preferably .NET) or tool with which I can create and apply patches? Ideally it should also handle small changes, like changing dependencies on a project level or tweaking a few lines in the source. It does not have to be

In a .net application involving several projects in one solution, I have a project with the namespace set to Company.Product.UI and another one with Company.Product.UI.WebPages. My problem is that two dlls result from building the two projects. How can I have a single dll and still preserve the current solution structure. I use Visual Studio 2008 and C#. You will have to either merge the two projects into one project or use a tool like ILMerge to merge the resulting assemblies into a single assembly. ILMerge is a utility that can be used to merge multiple .NET assemblies into a single assembly