assemblies

问题 all questions refer to Web site projects. 1) Why are file classes inside App_Code folder automatically referenced by the rest of application, while file classes created outside App_Code aren’t? 2) I don’t know much about compilation, but why do we need to explicitly reference class files created outside App_Code? Because those files will be compiled into dlls created and named by programmer and as such VS doesn’t know what the names of these dlls and so can’t automatically reference these

问题 So I'm trying to set up a project using the NDepend API for some metrics on my code (Which works nicely), however, when I attempt to run a testing framework (NUnit) over it, I'm getting TypeInitializationExceptions thrown. Here is some code to reproduce the errors I'm getting: Create a class library project, and reference the NDepend API dll at $NDependInstallPath$\lib\NDependAPI , setting copy local to false . Create a class as follows: public class NDependProjectLoader { public void

问题 I have 2 assemblies lets call them A and B. I've assigned strong names to them and now the problem arises that assembly B is looking for the old version of assembly A. **EDIT2: If I delete AssemblyB the problem persists so it might just be VS2008 looking for the old version? Also via fusionlog I see the following warning: wrn application configuration file binding redirects disallowed. Does this have anything to do with it? ** I get multiple errors of the same kind, here's one snippet: You

问题 Please describe the .NET assembly compilation circular dependency problem in layman's terms, and whether other technologes have similar limitations. Note: This seems like a simple question, I know, but I have seen a number of real, significant projects that have totally broken dependency graphs. 回答1: To add to Lucas's answer: it's very hard to come up with a circular assembly dependency in .NET. In order to compile A.dll you first need B.dll ; to compile B.dll you first need C.dll ; but to

问题 I observe unmanaged.dll files having a unmanaged.dll.manifest file tagging along. On opening this files in an editor, it seems to be normal XML with links to certain other dependent managed? assemblies. This seems to be like a recent change.. don't remember seeing them earlier. Why are these files needed? (If I had to make a guess, it would be to load dependent managed assemblies and/or the CLR) What other useful information can these files contain? Would they contain any links to dependent

问题 The MVVM approach encourages (or just gives the possibility to) splitting a WPF or Silverlight application into Model , ViewModel and View projects so all three could exist in their own assemblies. Using Prism (and, in my case, MEF as a Dependency Injection Container), on the other hand, one can build a modular application that is divided into a set of functional units (named modules) and each unit, in this case, is a seperate assembly. Am I right that in this case we can separate only a

问题 Im trying to setup what I think is a simple assembly, taking the jars from several modules and putting them in a specific folder inside a zip. The resulting assembly should look like so: ir4job\ ir4job\app_lib\ ir4job\app_lib\ jar files go here But maven is giving me an empty zip file when the assembly is generated Assembly descriptor: <assembly> <!-- ir4job folder contents --> <id>ir4job-app</id> <formats> <format>zip</format> </formats> <includeBaseDirectory>false</includeBaseDirectory>

问题 I have an assembly I would like to load from a sub-folder of the appbase. I set that sub-folder in the PrivateBinPath during AppDomain creation. The issue is that I have another version of the same DLL in the appbase. From the way it looks, the resolver detects the wrong version first, says that there is a mismatch and stops. As a result the correct version (located in the sub-folder) never gets loaded. I have tested this by removing those DLLs in the appbase and it fixed the problem. Is

问题 Background When creating general class libraries, I mirror the Microsoft .NET Framework name structure, replacing System with my own company name -- i.e., Tek4.Net.NetworkWidget . For product-specific assemblies, I use something like Tek4.ProductName.IO.FileWriter . Output .exe file names too long!!! Company.Product.SuperApp.exe Visual Studio uses the full assembly name for output files; this is great for DLL's, but is too much for a console application -- i.e., Tek4.Utils.ConsoleApp.exe

问题 I'm very interested in the CachedAssemblyCatalog class introduced in the samples provided in older versions of MEF - which allows loading a small assembly containing just the export data instead of the entire assembly, and only loading the full assembly when a part from that assembly is required. I'd like to use this feature in my application, but I'm not really sure about the stability/reliability of this code, and whether there are any future plans regarding this feature. Is it scheduled to