mod Dependency (non Freudian)

[rahzan]

If an External Dependency on a mod file (say for a lib) is created in a project it seems impossible to delete that particular path to have it look elsewhere for the mod file.

In this case I had a test main program which called a module, but I really need to use the module as library for the real application. Initially they were all one project so the external dep. of the main looked for the mod file in its debug folder. But now the module is in its own library, I cannot get the tester main project to let go of the old dependency and give it the updated mod file.

Any ideas?

Thanks, Tim

[Steven_L_Intel1]

I'm somewhat confused by your question. mod files don't go in libraries.

If you have a dependence on a module that has changed, Build..Update All Dependencies should take care of it.

Library files don't show up under External Dependencies.

Steve