understanding dependency between dll and vob's

[Sonali]

Hi, I am new to this group. I am working on a peice of code which is
like:
1 windows class library project which needs a startup project (exe
generated by other project). It references this exe and lots of other
dll's. These dll's and exe are located in our clearcase VOBs, though
I
have a local copy of them which I reference from my project. I am
working on Visual Basic.Net 2005.

The problem is: everytime I run my project, though the dll's are
copied and referenced from my local directory, they still reference
the VOB (I believe this because if there is no network connection,
the
project hangs...).


The question is: can you help me figure out a way to detect the
dependency on the vob and eliminate it (hopefully, there is a way of
doing it....)


I am new to Visual studio environment and programming... ANy help/
suggestions would be greatly appreciated...


Thanks,
Sonali

 

[VJ]

Just select the reference in the project (Solution explorer -> <Project> ->
Reference -> <Specific reference>). Hit F4 key now, opens the properties
window. Select Copy local = true. This keeps a local copy in your project
bin/debug directory. I hope I answered your question.

VJ

 

[Sonali]

Thanks for the reply. It is already set to true. Any other guess why
it might be linking... I just saw that when I run my application, it
creates a log files in the VOBs... any idea why that would be the
case, when it could hve done the same in application's bin directory?

Thanks again,
Sonali

 

[VJ]

Oh I get it.. maybe there is code in the directory that is forcing to go to
VOB by default. What I mean is Assembly.Load("") can be used as code to load
assembly from specific location, that override reference. The other
possibility is that there is a app.config sitting with app that does a
re-direct to the VOB.

Let me know if you see a app.config or any code that does specific load.. If
not both then you can start your application in debug mode and watch the
Output window to see where it picks the dlls or references from, it will be
VOB. Using that output window we can try to narrow down what is happening

HTH
VJ

 

[Sonali]

Thanks for ur prompt replies... I do not see any Assembly.Load used
anywhere.. However I am still double checking....

When I start the project in debug mode, it does reference the files
from VOB and I can walk through the entire code for those
dll's....which should not have happened......


Is there any specific place where you can look for the app.config
file?

I am looking at all the places I can think off....

Regards,
Sonali

 

[VJ]

Sonali,

First look at app.config in your project.. or even if there is one for the
application

We will keep walking through as last option. If the output window shows so,
then there is a problem at the begin of the project.

VJ

 

[VJ]

Oh just remembered this one other possible place is the Reference path
location for the project in Project -> Properties..

Please chk this and app.config.

VJ

 

[Sonali]

VJ,

The reference path for all dll's is set correctly. They all seem to
refer to the folder in my project (which they should).... I do not see
any app.config file.. Could you please tell me if its present in a
specific directory or something... I have looked at almost all the
files n directories in my project folder....

Sonali

 

[VJ]

Now this is strange. If there is not a app.config. See in the application's
exe directory for a file like this <appname>.exe.config, That is the
complied App.Config

I am starting to believe, not all related references are being copied if you
set copy local to true?.. Do you see all your applications exe and Dll's in
the executable directory?..

Also as a possibility, and thinking out the box, is it missing some other
file like a resource or something and it hangs on it?. Did you clearly
establish that is it because of Dll or binary? Is your Visual Studio hanging
or running the application is hanging? There is a difference. If its clearly
Visual Studio hanging then it could be some resource file or some other file
its missing and looking for it in the VOB

VJ