.net-assembly

I am loading another assembly using Assembly.LoadFrom("path.exe"); and after that i cant seem to delete that exe from the file system. so i was wondering if this path keeps an open file handle and how i can close it? Cédric Bignon Yes, it is open until the assembly is unloaded from the appdomain. If you really need to delete the file, load its content into memory. The use Assembly.Load(byte[]) to load the assembly: using (Stream stream = File.OpenRead("path.exe")) { byte[] rawAssembly = new byte[stream.Length]; stream.Read(rawAssembly, 0, (int)stream.Length); Assembly.Load(rawAssembly); } By

Say I've a class like this inside a class library project called SomeClass- Public Class SomeClass Public Function DoIt() as String Return "Do What?" End Function End Class I get a SomeClass.dll which I want to load at runtime from another Windows Forms Application, and then have it call the DoIt() function and show it's value in a messagebox or something. How do I do that? I suggest to make DoIt shared, since it does not require class state: Public Class SomeClass Public Shared Function DoIt() as String Return "Do What?" End Function End Class Then calling it is easy: ' Loads SomeClass.dll

I'm trying to publish an ASP.NET MVC 4 Internet Application. After it's been published, I go ahead and click the link for my website and find this: Server Error in '/' Application. Could not load file or assembly 'System.Web.Http, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.IO

(1) Using the code below I get exactly 2 items in my containers of one and the same exported plugin and I wonder why: (2) Additional question which I really cannot implement: How can I extend the framework to handle different plugin types (such as having several imports of different types, or one import that stores all plugins in a dynamic IEnumerable or so). I want to provide in my static wrapper class one generic method that returns the discovered plugin as a function of type and matching meta data. The exported plugin (which resides in a separate dll and whose location is pointed to when

There are quite a few questions/answers about the compiler error mentionend below and how to resolve it, but the question here is asking about some insights why in this case this is required. Why does a project A which uses an overload of a method of another referenced project B, which uses an object of project C in one of it's overloaded signatures require, that you reference project C from project A, even if you never use the object from project C? I guess it must have to do with the resolving of which overload to use, but I'd like to understand the concept behind. Here's an example: Put

Ok I understand that this is probably not conventional, but that aside: I am using the AssemblyFileVersion as kind of my "Build Name" string. It is formated like this: ' File Version information for an assembly consists of the following four values: ' ' Year ' Month ' Day ' Commit Number for that day ' ' Build Name can either be alpha | beta | hotfix | release ' alpha - is a development buildname with rapid changing API ' beta - is a production build for our beta users ' hotfix - is a production version with a bug fix ' release - is a standard issue production version. <Assembly: