reflector

When I'm debugging or even coding, it would be really uesful to examine third party assemblies but I can only see their metadata. Given that tools like reflector can decompile assemblies, is there someway or some tool which would allow visual studio to do the same thing? If I happen to have access to the PDB files for an assemblies, would placing them into my applications bin folder allow me to examine the assemblies content through visual studio? If you have PDB's for a DLL you can certainly examine the DLL while debugging. Make sure that you have "Just My Code Disabled" and you should be

When I was looking at the Action delegates in Reflector, I saw it has a constructor like public Action(object @object, IntPtr method); But I could not find any body for the same along with other member functions like Invoke , BeginInvoke etc. I can only see the definitions for it. Where does these functions are defined? Are they defined outside of the .net BCLs? Delegates are handled specially by the CLR, basically. The compiler provides the signatures, but the CLR knows what to do with them. Section 8.9.3 of ECMA-335 partition I talks about this: Delegates are the object-oriented equivalent

I am doing work for a client who has lost the source code for one of their VB.Net WinForms applications. The assembly they have is not obfuscated at all. I am trying to recover as much of the source as I can as C# source and have tried several tools for decompiling assemblies, including Reflector, ILSpy and JustDecompile (all the latest versions), but they all produce code with a huge number of errors in them. Because of the large number of errors in the generated code, I am going to ask about the specific errors (in different questions), hopefully to get more directed answers and in this way

So this is how you invoke Main() in non WPF applications: var entry = assembly.EntryPoint; if (assembly.EntryPoint.GetParameters().Length == 0) entry.Invoke(null, new object[0]); else entry.Invoke(null, new object[] { args }); but somehow it doesn't work at all for WPF applications, I've tried (MSDN's way): Assembly asm = Assembly.LoadFrom(file); Type myType = asm.GetType("WpfApplication1.App"); // Get the method to call. MethodInfo myMethod = myType.GetMethod("Main"); // Create an instance. object obj = Activator.CreateInstance(myType); // Execute the method. myMethod.Invoke(obj, null); still

I had to de-compile some code and I don't know what this syntax is? Can y'all help, or point me to a write-up about what it is? I've Googled and searched this site and can't find anything. Just one line of code: Rectangle pageBounds; // ISSUE: explicit reference operation // ISSUE: variable of a reference type Rectangle& local = @pageBounds; What is the @ symbol at the end of the Rectangle object type, and the @ before the pageBounds variable? This is my last line of code that I need to fix in order to get this executable to compile again. Here's the method that uses this syntax, can I get

I have a .exe app which I want to understand better - I can see it in reflector Is there any way to get reflector to create a VS project with the code so I can view it properly in Visual Studio? Nothing special is needed, it is built into Reflector, albeit not very discoverable. Right-click the assembly in the left pane and choose Export. You'll get a chance to change the output directory. Click OK and Reflector starts decompiling the code, creating a source file for each individual class. And creates a .csproj file which you can open in Visual Studio. Check out Jason Bock's FileGenerator , it