Thanks for your help, Nicolas, this is making me crazy.
Im referencing a function in another assembly (which is in a project within
the same solution, the project only contains classes) that I have a reference
to - see the diagram below. This has always worked in my other apps, Ive
never seen this "[from metadata]" until now.
Something that might help - in all my other apps, when I make a change to a
class in ClassProject (such as adding a public property), the change becomes
available immediately. In this instance of vs.net I have to compile
ClassProjectbefore the change is visible to ASPNETProject.
MySolution <-- solution
ClassProject <-- classes
ASPNETProject <-- asp.net app, has reference to ClassProject
"Nicholas Paldino [.NET/C# MVP]" wrote:
Mark,
Are you referencing the assembly, or the project? If you are
referencing an assembly, then I would expect to get the "[from metadata]".
If you are referencing the project, then I would assume you would go to the
code where the method is implemented.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com
"SandpointGuy" <Sa**********@discussions.microsoft.comwrote in message
news:76**********************************@microsof t.com...
Not sure if this is a vs.net question, but since its happening in Im
looking
at c# code ...
I often double-click on a method to highlight it, right click, and choose
"Go To Definition" to view a method. Ive done this in vs 1.1 and other vs
2.0 instances on other computers. On my new laptops (XP Pro) vs 2.0, when
I
do this it brings up a "<Class name[from metadata]", which is the
correct
class and its signatures (like a interface), but not the implementation
code.
What is causing this to happen (so I can stop it!)
Thanks, Mark