Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

dll problems...

Status
Not open for further replies.

FederalProgrammer

Programmer
Jul 2, 2003
318
CA
This is a weird one:

I have a main "Toolbox" written in vb .NET; It is an mdi parent to millions of other tools that is developed by our developers. We have included these tools as .dlls (references) in this "Toolbox". We have build scrips that builds each of these tools and puts them in a "reference" folder (that includes all the references used by the "Toolbox").

When I want to debug any of the tools, I simply build the tool and put its .dll in the reference folder; Then I open the file that I want to put my break point, in "Toolbox" solution and Run Toolbox and walah...

In short:
Code:
Toolbox: main container
Reference folder: contains all the .dlls used by toolbox
Other tools: are built and their .dlls is placed in Reference folder
Debuggin other tools: Make sure the tool is build into Reference folder; Open the file in "Toolbox"; put a break point;

My Question:
I am having difficulty w/ one of the files that I'm trying to debug!! When I run Toolbox and I put a break point on line X of File "blah.vb", another copy of file "Blah" is opened and my break point on line X gets translated to some other line number!!! and even though there are two copies of file "Blah.vb" is open (one of them opened by me and the other is opened on its own when I try to put a break point), the two files are not the same (it seems like the copy that I don't open is an older version of file "Blah.vb"!!)

In short:
Code:
I put a break point in one of the files I want to debug (file "blah.vb");
when I run toolbox, an older version of file "blah.vb" is opened!! 
Even when I try to put a break point by the original "blah.vb", the older version gets the break point!!
I have made sure to build all of the files in debug mode. Also "Toolbox" is being run in debug mode!! What am I doing wrong?
Any ideas?? Anything... I know it must be something stupid that I'm overlooking... so feel free to suggest just about anything!!


cheers!








why do they call it VB.NET? it's nothing like vb; they should've called it B#!!
 
hmmmm,
Heres' what I think is happening... apparently some of our developers, have developed two different .dlls w/ similar names!! it's only the name space that is different!!
So, "blah.vb" can be found in two different locations... one of these "blah.vb" that I was openning was apparently not the one I was looking for!!! so VS is trying to be smart and it switches my breakpoint to the correct "blah.vb"!!! At lease this is what I think is the case....

Anyways, please don't concern yourself w/ this thread any more...


Cheers!


visit my website:

why do they call it VB.NET? it's nothing like vb; they should've called it B#!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top