Comments
2 comments
-
We'll certainly take a look at this. I've added an entry into the bug tracking system to investigate.
Reflector has the "Export" context menu item which is available when an assembly is selected. This generates code with appropriate using statements and we may be able to hook into that. -
This is done now. Unfortunately it doesn't really fix intellisense, but it'll help you manually see the namespaces of things.
Add comment
Please sign in to leave a comment.
I met Clive at PDC '09 a few days ago, whom turned me onto the Pro version of Reflector. Very cool stuff.
Using build 506, I was able to decompile a target assembly and create a project based on existing code. This allowed me to exploit some of the Intellisense capabilities in Visual Studio, but there are still some gaps.
For example, the assembly I targeted contains multiple namespaces. The output decompiled code does not reference any namespaces, therefore VS runs into a wall.
I understand that parsing the code and detecting namespace usage may be a nightmare. I think it may be 'good enough' to allow users to inject a list of namespaces at decompilation time that would be added to the top of each source file.
Thoughts?
/rafael