assemblies

I recently bought Ayende's book Building DSLs in Boo (buy it, read it, it's awesome) but I'm coming up against an implementation problem and I want to see what the generated code looks like. I would normally use reflector to look at the code but in this case the assemblies are dynamic and only in memory. Is there a way to save dynamic assemblies to disk so that I can reflect them? EDIT / My Answer : Wow, it took awhile to come back to this one. Unfortunately I left an important bit out from the original question. Important Bit: I'm using Ayende's RhinoDSL library as he recommends in the book.

I have an assembly, Foo, which has a reference to assembly Bar (version X.X.X.2000). In the properties, the specific version is set to False. I have both Bar (x.x.x.2000) and Bar (x.x.x.1000) in my local GAC . Everything is fine. On another machine, where no version of Bar is in the GAC, but Bar (x.x.x.1000) is located in the same directory as Foo, running Foo will fail claiming it can not find Barr (x.x.x.2000) with Could not load file or assembly 'Bar, Version=x.x.x.2000, Culture=neutral, PublicKeyToken=YXYXYXYXXYX' or one of its dependencies. The located assembly's manifest definition does

Possible Duplicate: Merging .net managed dlls I create a test project in which I referenced a dll from some other project. When I build my test project, I see different dll for test project and the referenced dll. I want to wrap both dll's in a single dll. How can I do it. Take a look at ILMerge: http://www.microsoft.com/downloads/en/details.aspx?familyid=22914587-b4ad-4eae-87cf-b14ae6a939b0&displaylang=en http://www.codeproject.com/KB/dotnet/mergingassemblies.aspx With ILMerge you can merge a bunch of assemblies by running the command like: ilmerge /out:MergedAssembly.dll ProjectAssembly1.dll

Is there any way to know in C# the type of application that is running. Windows Service ASP.NET Windows Form Console I would like to react to the application type but cannot find a way to determine it. You should have the client code tell your code what the context is and then work from that. At best, you will be able to guess based on external factors. If you must guess, this is what I would look for: For ASP.NET, I would look for HttpContext.Current For Windows Forms, I see if the static OpenForms collection on the Application class has any items in it. For Windows Presentation Foundation,

Could anyone point out the advantage of using assemblies, in the 'context' of ASP.NET . As I understand it, assemblies run as executables, have a single entry point, and can be run inside an application domain, but I've found very few suitable examples on the web. An assembly is not just an executable... an assembly is essentially a .NET library that may have an executable entry point... Wikipedia article with description of assemblies First paragraph: In the Microsoft .NET framework, an assembly is a partially compiled code library for use in deployment, versioning and security. There are two