473,325 Members | 2,860 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,325 software developers and data experts.

"go to definition" problem. What changed?

I was thinking of switching to VS2005, so I sent off for and received a 120
evaluation kit. This version was supposed to be the same as the full
version, but the key limits you to 120 days. I installed it and began
learning how to use it.

I built several small C# test apps that use common classes in a dll that I
also wrote. When I right click on a class that was defined in the dll and
select "go to definition" it would open the source file from the dll
project. Great!

I decided to buy VS2005... After installation of the purchased version the
"go to definition" doesn't work the same way. It always opens a meta data
fragment. In most cases I am more interested in my comments in the actual
source, or something near the item I right clicked on.

According to the docs VS does this when it can not find the source. I
don't quite understand this because I am opening the SAME solutions that
were created with the eval version and everything looks the same.

I have tried adding the dll to the current solution, not just the
reference, but I still won't find it. Even if I have the source file open
in another tab.

If I right click on a class or variable in the "other tab" and select "go
to definition" where the definition is elsewhere in the same file I get a
runtime error and VS closes!

If I run my app, I can trace into the actual source of the dll, so why cant
the "go to reference" find it?

This is very annoying.

Can anyone help?
Oct 26 '07 #1
5 5902
Hi,

If it does do that is cause it has no knowledge of where the source code is.

You can include the other's prject in your solution and it will work as
expected.

--
Ignacio Machin
http://www.laceupsolutions.com
Mobile & warehouse Solutions.
"Fred Hebert" <fh*****@hotmail.comwrote in message
news:Xn*******************************@207.46.248. 16...
>I was thinking of switching to VS2005, so I sent off for and received a 120
evaluation kit. This version was supposed to be the same as the full
version, but the key limits you to 120 days. I installed it and began
learning how to use it.

I built several small C# test apps that use common classes in a dll that I
also wrote. When I right click on a class that was defined in the dll and
select "go to definition" it would open the source file from the dll
project. Great!

I decided to buy VS2005... After installation of the purchased version the
"go to definition" doesn't work the same way. It always opens a meta data
fragment. In most cases I am more interested in my comments in the actual
source, or something near the item I right clicked on.

According to the docs VS does this when it can not find the source. I
don't quite understand this because I am opening the SAME solutions that
were created with the eval version and everything looks the same.

I have tried adding the dll to the current solution, not just the
reference, but I still won't find it. Even if I have the source file open
in another tab.

If I right click on a class or variable in the "other tab" and select "go
to definition" where the definition is elsewhere in the same file I get a
runtime error and VS closes!

If I run my app, I can trace into the actual source of the dll, so why
cant
the "go to reference" find it?

This is very annoying.

Can anyone help?

Oct 26 '07 #2
Not to be picky, but I have already tried that...
According to the docs VS does this when it can not find the source. I
don't quite understand this because I am opening the SAME solutions
that
were created with the eval version and everything looks the same.

I have tried adding the dll to the current solution, not just the
reference, but I still won't find it. Even if I have the source file
open
in another tab.

Initially I created the DLL as a stand alone solution.

Next I created a new Windows Form solution. I added a reference to the
DLL (Add Reference>Browse and double click on the actual dll). I got
this from an example...

I added a using MyDllNamespace statement and created some instances of a
couple of the classes in the dll.

Compiled and ran, all OK, and I could just right click and "go to
definition" and it would take me to the actual source in the dll
project.

After install of the full version, I open the SAME Windows Form solution
that was previously created and the "go to definition" gives me
metadata.

I tried to Add Existing Project to the solution and add the dll project,
but it did not fix the metadata problem.

I am new to VS (but not programming). What am I missing?

If it matters it is VS2005 pro...
"Ignacio Machin \( .NET/ C# MVP \)" <machin TA laceupsolutions.com>
wrote in news:e3**************@TK2MSFTNGP02.phx.gbl:
Hi,

If it does do that is cause it has no knowledge of where the source
code is.

You can include the other's prject in your solution and it will work
as expected.
Oct 26 '07 #3
"Fred Hebert" <fh*****@hotmail.comschrieb im Newsbeitrag
news:Xn*******************************@207.46.248. 16...
>
Initially I created the DLL as a stand alone solution.

Next I created a new Windows Form solution. I added a reference to the
DLL (Add Reference>Browse and double click on the actual dll). I got
this from an example...
<snip>
>
Compiled and ran, all OK, and I could just right click and "go to
definition" and it would take me to the actual source in the dll
project.
I'm not sure, why this works. I wouldn't expect this.
After install of the full version, I open the SAME Windows Form solution
that was previously created and the "go to definition" gives me
metadata.

I tried to Add Existing Project to the solution and add the dll project,
but it did not fix the metadata problem.
I suppose you still linking to the dll instead of the project.

Remove the reference, and then choose add reference and select the dll
project from the projects tab. That should work.

HTH
Christof

Oct 26 '07 #4
BINGO!

Thanks.

Sometimes it's the little things...

I am not sure why the other worked either. The eval version did have
some other stuff like team source and other things. The version I
bought was the Professional, not the enterprise...

I am just glad I have a solution, because I use that al lot.

I am developing/comverting a large app with 17 variants and putting the
common code in the dll. So I am sort of building both projects in
parallel and go back and forth a lot.

Thanks.

"Christof Nordiek" <cn@nospam.dewrote in news:ulfqwF#FIHA.4956
@TK2MSFTNGP06.phx.gbl:
"Fred Hebert" <fh*****@hotmail.comschrieb im Newsbeitrag
news:Xn*******************************@207.46.248. 16...
>>
Initially I created the DLL as a stand alone solution.

Next I created a new Windows Form solution. I added a reference to
the
>DLL (Add Reference>Browse and double click on the actual dll). I got
this from an example...
<snip>
>>
Compiled and ran, all OK, and I could just right click and "go to
definition" and it would take me to the actual source in the dll
project.

I'm not sure, why this works. I wouldn't expect this.
>After install of the full version, I open the SAME Windows Form
solution
>that was previously created and the "go to definition" gives me
metadata.

I tried to Add Existing Project to the solution and add the dll
project,
>but it did not fix the metadata problem.
I suppose you still linking to the dll instead of the project.

Remove the reference, and then choose add reference and select the dll
project from the projects tab. That should work.

HTH
Christof

Oct 26 '07 #5
You do realise that VS2008 is avaliable next month??

--
--
Bob Powell [MVP]
Visual C#, System.Drawing

Ramuseco Limited .NET consulting
http://www.ramuseco.com

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.
"Fred Hebert" <fh*****@hotmail.comwrote in message
news:Xn*******************************@207.46.248. 16...
>I was thinking of switching to VS2005, so I sent off for and received a 120
evaluation kit. This version was supposed to be the same as the full
version, but the key limits you to 120 days. I installed it and began
learning how to use it.

I built several small C# test apps that use common classes in a dll that I
also wrote. When I right click on a class that was defined in the dll and
select "go to definition" it would open the source file from the dll
project. Great!

I decided to buy VS2005... After installation of the purchased version the
"go to definition" doesn't work the same way. It always opens a meta data
fragment. In most cases I am more interested in my comments in the actual
source, or something near the item I right clicked on.

According to the docs VS does this when it can not find the source. I
don't quite understand this because I am opening the SAME solutions that
were created with the eval version and everything looks the same.

I have tried adding the dll to the current solution, not just the
reference, but I still won't find it. Even if I have the source file open
in another tab.

If I right click on a class or variable in the "other tab" and select "go
to definition" where the definition is elsewhere in the same file I get a
runtime error and VS closes!

If I run my app, I can trace into the actual source of the dll, so why
cant
the "go to reference" find it?

This is very annoying.

Can anyone help?
Oct 28 '07 #6

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

6
by: Dave | last post by:
I have a stored procedure in sql 2000 that requires steps to be fully completed before moving to the next command in the procedure. I have tried to place the word "GO" after each statement. When I...
2
by: Hartmut Sbosny | last post by:
Hello NG, I have a question. I have a header file with a function template and a fully specialized version of it, for instance //======== File "templ.hpp" ======== #include <iostream> // the...
17
by: Will Hartung | last post by:
I have a table for a report. It can get wide, but that's no big deal. I don't mind that it can get wide. What I do mind, though, is the browser doing its damndest to smash the thing down to get...
10
by: Kobu | last post by:
My question is about the use and meaning of the terms "declaration" and "definition" as it pertains to the C language. I've read sources that mix the two up when talking about such things as...
1
by: CA | last post by:
I am having a problem getting a pointer to an existing running Excel process on a client machine. Here are some details: 1) I have tested out the code on the development machine and it works...
0
by: mavis | last post by:
Does IntellJ support the checking for "keyref" definition? Why it seems does not work at all? <xs:key name="supported-platforms-name-unique"> <xs:selector...
7
by: Rob | last post by:
In a previous thread, I was asking about setting up my global.aspx which inherits System.Web.HttpApplication. This is where there are the event handlers like: Sub Session_Start(ByVal sender As...
0
by: Tequilaman | last post by:
Has anybody here every created a program to insert data from a csv into a webform, including a click to a 'go on' button and choosing in dropdowns according to the information in the csv? I'm...
0
by: DR | last post by:
when i build someone's project, and right click a function "goto definition" is disabled. how to reconfigure a .net project to support "goto definition" when i right click on function calls?
0
by: ryjfgjl | last post by:
ExcelToDatabase: batch import excel into database automatically...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
1
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: Vimpel783 | last post by:
Hello! Guys, I found this code on the Internet, but I need to modify it a little. It works well, the problem is this: Data is sent from only one cell, in this case B5, but it is necessary that data...
0
by: jfyes | last post by:
As a hardware engineer, after seeing that CEIWEI recently released a new tool for Modbus RTU Over TCP/UDP filtering and monitoring, I actively went to its official website to take a look. It turned...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
1
by: PapaRatzi | last post by:
Hello, I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...
1
by: CloudSolutions | last post by:
Introduction: For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
0
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome former...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.