**Using Visual Studio**

1. Attach a debugger to the process (e.g. start with debugging or Debug &gt; Attach to process)
2. While debugging, show the Modules window (Debug &gt; Windows &gt; Modules)

This gives details about each assembly, app domain and has a few options to load symbols (i.e. pdb files that contain debug information).

[![enter image description here][1]][1]

**Using Process Explorer**

If you want an external tool you can use the [Process Explorer][2] (freeware, published by Microsoft)

Click on a process and it will show a list with all the assemblies used. The tool is pretty good as it shows other information such as file handles etc. 

**Programmatically**

Check [this SO][3] question that explains how to do it.


  [1]: http://i.stack.imgur.com/vEhgX.png
  [2]: http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
  [3]: https://stackoverflow.com/questions/383686/how-do-you-loop-through-currenlty-loaded-assemblies

Here&#39;s what I ended up with.  It&#39;s a listing of all properties and methods, and I listed all parameters for each method.  I didn&#39;t succeed on getting all of the values.

				

    foreach(System.Reflection.AssemblyName an in System.Reflection.Assembly.GetExecutingAssembly().GetReferencedAssemblies()){						
    			System.Reflection.Assembly asm = System.Reflection.Assembly.Load(an.ToString());
    			foreach(Type type in asm.GetTypes()){	
    				//PROPERTIES
    				foreach (System.Reflection.PropertyInfo property in type.GetProperties()){
    					if (property.CanRead){
    						Response.Write(&quot;&lt;br&gt;&quot; + an.ToString() + &quot;.&quot; + type.ToString() + &quot;.&quot; + property.Name);		
    					}
    				}
    				//METHODS
    				var methods = type.GetMethods();
    				foreach (System.Reflection.MethodInfo method in methods){				
    					Response.Write(&quot;&lt;br&gt;&lt;b&gt;&quot; + an.ToString() + &quot;.&quot;  + type.ToString() + &quot;.&quot; + method.Name  + &quot;&lt;/b&gt;&quot;);	
    					foreach (System.Reflection.ParameterInfo param in method.GetParameters())
    					{
    					    Response.Write(&quot;&lt;br&gt;&lt;i&gt;Param=&quot; + param.Name.ToString());
    					    Response.Write(&quot;&lt;br&gt;  Type=&quot; + param.ParameterType.ToString());
    					    Response.Write(&quot;&lt;br&gt;  Position=&quot; + param.Position.ToString());
    					    Response.Write(&quot;&lt;br&gt;  Optional=&quot; + param.IsOptional.ToString() + &quot;&lt;/i&gt;&quot;);
    					}
    				}
    			}
    		}

I have a series of ranges with start dates and end dates. I want to check to see if a date is within that range.

Date.before() and Date.after() seem to be a little awkward to use. What I really need is something like this pseudocode:

    boolean isWithinRange(Date testDate) {
        return testDate &gt;= startDate &amp;&amp; testDate &lt;= endDate;
    }

Not sure if it&#39;s relevant, but the dates I&#39;m pulling from the database have timestamps. 




How do I check if a date is within a certain range?

How do I pass parameters to a JAR file at the time of execution?


How do I pass parameters to a jar file at the time of execution?

In .Net, I would like to enumerate all loaded assemblies over all AppDomains. Doing it for my program&#39;s AppDomain is easy enough `AppDomain.CurrentDomain.GetAssemblies()`. Do I need to somehow access every AppDomain? Or is there already a tool that does this?

How do I list all loaded assemblies?

<p>In .Net, I would like to enumerate all loaded assemblies over all AppDomains. Doing it for my program's AppDomain is easy enough <code>AppDomain.CurrentDomain.GetAssemblies()</code>. Do I need to somehow access every AppDomain? Or is there already a tool that does this?</p>


I was looking at C# collection initializers and found the implementation to be very pragmatic but also very unlike anything else in C#

I am able to create code like this:

    using System;
    using System.Collections;
    
    class Program
    {
    	static void Main()
    	{
    		Test test = new Test { 1, 2, 3 };
    	}
    }
    
    class Test : IEnumerable
    {
    	public IEnumerator GetEnumerator()
    	{
    		throw new NotImplementedException();
    	}
    
    	public void Add(int i) { }
    }

Since I have satisfied the minimum requirements for the compiler (implemented `IEnumerable` and a `public void Add`) this works but obviously has no value.

I was wondering what prevented the C# team from creating a more strict set of requirements?  In other words why, in order for this syntax to compile, does the compiler not require that the type implement `ICollection`?  That seems more in the spirit of other C# features.
 

Why do C# collection initializers work this way?

Is there a VB.NET equivalent to the C#:

    public string FirstName { get; set; }

I know you can do 

    Public Property name() As String
       Get
          Return _name.ToString
       End Get
       Set(ByVal value As String)
           _name = value
       End Set
    End Property

But I can&#39;t seem to google up an answer on a Visual Basic shorthand.


VB.NET equivalent of C# property shorthand?

Is it possible to deploy a Windows Service using ClickOnce? If so, how do you achieve this?

Currently we have to use a Deployment project, and the installation process could be simplified greatly by using ClickOnce.



ClickOnce deploy a Windows Service?

I am currently writing a small framework that will be used internally by other developers within the company.

I want to provide good Intellisense information, but I am not sure *how* to document thrown exceptions.

In the following example:

    public void MyMethod1()
    {
        MyMethod2();

        // also may throw InvalidOperationException
    }

    public void MyMethod2()
    {
        System.IO.File.Open(somepath...); // this may throw FileNotFoundException

        // also may throw DivideByZeroException
    }

I know the markup for documenting exceptions is:

    /// &lt;exception cref=&quot;SomeException&quot;&gt;when things go wrong.&lt;/exception&gt;

What I don&#39;t understand is how to document exceptions thrown by code **called by** `MyMethod1()`?


* Should I document exceptions thrown by `MyMethod2()`
* Should I document exceptions thrown by `File.Open()` ?


What would be the best way to document possible exceptions?

How to document thrown exceptions in c#/.net

I&#39;m looking for a function that will convert a standard IPv4 address into an Integer.  Bonus points available for a function that will do the opposite.

Solution should be in C#.

How to convert an IPv4 address into a integer in C#?

When developing a .NET Windows Forms Application we have the choice between those `App.config` tags to store our configuration values. Which one is better?

    &lt;configuration&gt;

      &lt;!-- Choice 1 --&gt;
      &lt;appSettings&gt;
        &lt;add key=&quot;RequestTimeoutInMilliseconds&quot; value=&quot;10000&quot;/&gt;
      &lt;/appSettings&gt;

      &lt;!-- Choice 2 --&gt;
      &lt;configSections&gt;
        &lt;sectionGroup name=&quot;applicationSettings&quot; type=&quot;System.Configuration.ApplicationSettingsGroup, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c5612342342&quot; &gt;
            &lt;section name=&quot;Project1.Properties.Settings&quot; type=&quot;System.Configuration.ClientSettingsSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c5612342342&quot; requirePermission=&quot;false&quot; /&gt;
        &lt;/sectionGroup&gt;
      &lt;/configSections&gt;
      &lt;applicationSettings&gt;
        &lt;Project1.Properties.Settings&gt;
          &lt;setting name=&quot;TABLEA&quot; serializeAs=&quot;String&quot;&gt;
            &lt;value&gt;TABLEA&lt;/value&gt;
          &lt;/setting&gt;
        &lt;/Project1.Properties.Settings&gt;
      &lt;/applicationSettings&gt;

    &lt;/configuration&gt;


Pros and cons of AppSettings vs applicationSettings (.NET app.config / Web.config)

In .Net (C# or VB: don&#39;t care), given a file path string, FileInfo struct, or FileSystemInfo struct for a real existing file, how can I determine the icon(s) used by the shell (explorer) for that file?

I&#39;m not currently planning to use this for anything, but I became curious about how to do it when looking at [this question][1] and I thought it would be useful to have archived here on SO.


  [1]: https://stackoverflow.com/questions/462232/what-is-the-best-vb-net-control-standard-custom-for-displaying-list-of-files

Get File Icon used by Shell

I read in the Essential C# 3.0 and .NET 3.5 book that:

&gt;GetHashCode()’s returns over the life of a particular object should be
constant (the same value), even if the object’s data changes. In many
cases, you should cache the method return to enforce this.

Is this a valid guideline?

I have tried a couple built-in types in .NET and they didn&#39;t behave like this.



GetHashCode Guidelines in C#

What is the significance of the two keywords [Shadows][1] and [Overrides][2]? What they do and for which context is one or the other preferable?

  [1]: http://msdn.microsoft.com/en-us/library/1h3wytf6.aspx
  [2]: http://msdn.microsoft.com/en-us/library/k777kzw1.aspx


&#39;Shadows&#39; vs. &#39;Overrides&#39; in VB.NET

Is it possible to instantiate an object at runtime if I only have the DLL name and the class name, without adding a reference to the assembly in the project? The class implements a interface, so once I instantiate the class, I will then cast it to the interface.

Assembly name:
&gt; library.dll 

Type name: 
&gt;Company.Project.Classname

----
**EDIT:** I dont have the absolute path of the DLL, so `Assembly.LoadFile` won&#39;t work. The DLL might be in the application root, system32, or even loaded in the GAC.

Can I load a .NET assembly at runtime and instantiate a type knowing only the name?

How do I find out the fully qualified name of my assembly such as:

    MyNamespace.MyAssembly, version=1.0.3300.0, 
    Culture=neutral, PublicKeyToken=b77a5c561934e089

I&#39;ve managed to get my PublicKeyToken using the `sn.exe` in the SDK, but I&#39;ld like to easily get the full qualified name.



How do I find the fully qualified name of an assembly?

I want to load to a new `AppDomain` some assembly which has a complex references tree (MyDll.dll -&gt; Microsoft.Office.Interop.Excel.dll -&gt; Microsoft.Vbe.Interop.dll -&gt; Office.dll -&gt; stdole.dll)

As far as I understood, when an assembly is being loaded to `AppDomain`, its references would not be loaded automatically, and I have to load them manually.
So when I do:

    string dir = @&quot;SomePath&quot;; // different from AppDomain.CurrentDomain.BaseDirectory
    string path = System.IO.Path.Combine(dir, &quot;MyDll.dll&quot;);
    
    AppDomainSetup setup = AppDomain.CurrentDomain.SetupInformation;
    setup.ApplicationBase = dir;
    AppDomain domain = AppDomain.CreateDomain(&quot;SomeAppDomain&quot;, null, setup);

    domain.Load(AssemblyName.GetAssemblyName(path));
and got `FileNotFoundException`: 

&gt; Could not load file or assembly &#39;MyDll, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null&#39; or one of its dependencies. The system cannot find the file specified.

I think the key part is **one of its dependencies**.

Ok, I do next before `domain.Load(AssemblyName.GetAssemblyName(path));`

    foreach (AssemblyName refAsmName in Assembly.ReflectionOnlyLoadFrom(path).GetReferencedAssemblies())
    {
        domain.Load(refAsmName);
    }

But got `FileNotFoundException` again, on another (referenced) assembly.

How to load all references recursively?

Do I have to create references tree before loading root assembly? How to get an assembly&#39;s references without loading it?

How to Load an Assembly to AppDomain with all references recursively?

I have a few WPF applications and I want all my styles to be in a shared assembly instead of declaring them in each application separately.

I am looking for a way so I don&#39;t have to change all my `Style=&quot;{StaticResource BlahBlah}&quot;` in the existing applications; I just want to add the reference to this style assembly, and delete it from the current application, so it&#39;s taken from the assembly.

Is there any way?

Load WPF styles or other Static Resources from an external file or assembly

There is a package I have to deal with which installs assemblies straight into the GAC (e.g. somewhere deep in %windows%/assembly).  

How do I exorcise the actual assembly (the DLL) from the GAC into the normal file system?

Thanks.

Content Type	Original Author	Original Content on Stackoverflow
Question	Abtin Forouzandeh	View Question on Stackoverflow
Solution 1 - C#	Bogdan Gavril MSFT	View Answer on Stackoverflow
Solution 2 - C#	s15199d	View Answer on Stackoverflow

How do I list all loaded assemblies?

C# Problem Overview

C# Solutions

Solution 1 - C#

Solution 2 - C#

How do I pass parameters to a jar file at the time of execution?

How do I check if a date is within a certain range?

Attributions