I have a project (Project A) which is dependent upon serveral components (llblgen, Infragistics, etc)

Project A -> depends on llblgen Project A -> depends on Infragistics

My question is, what is the opposite of "depends on"

llblgen -> Is a dependent of Project A? Is "dependent" the correct word? Doesn't sound right?

Stupid question I know, but my brain is not working right now.

erichar11 wrote:

I have a project (Project A) which is dependent upon serveral components (llblgen, Infragistics, etc)

Project A -> depends on llblgen Project A -> depends on Infragistics

My question is, what is the opposite of "depends on"

llblgen -> Is a dependent of Project A? Is "dependent" the correct word? Doesn't sound right?

Stupid question I know, but my brain is not working right now.

I don't think there is an opposite of "depends on" other than "does not depend on".

And your ProjectA is a dependant of LLBLGen.

PS. The words dependent and dependant are interchangable.

Ok, agreed, maybe depends on is not the correct word. But what is? How would you describe the relationship betwee the two projects/components.

Project A -> "something here" Llblgen

and

Llblgen -> " something here " Project A

"Does not depend on" doesn't work. There is a relationship between the projects, I just can't figure out the appropriate words to explain that relationship.

Hope you see my wording problem.

To be a little bit more clear, in my app I have a dependency module. When a user selects on Project a, they can see other projects which they are dependent on.

i.e. (Project A) depends on Llblgen

Now a user can can select on LLblgen project in the app, and show it's relationships to other projects , however it's from the other side of the relationship and that's what's causing me wording problems.

llblgen-> "something here" Project A

erichar11 wrote:

To be a little bit more clear, in my app I have a dependency module. When a user selects on Project a, they can see other projects which they are dependent on.

i.e. (Project A) depends on Llblgen

Now a user can can select on LLblgen project in the app, and show it's relationships to other projects , however it's from the other side of the relationship and that's what's causing me wording problems.

llblgen-> "something here" Project A

How about...

llblgen -> prerequisite for -> Project A

How about...

llblgen -> prerequisite for -> Project A

hmmm..

Project A "depends on" llblgen llblgen " is a prerequisite for" Project A

will have to think about that. It's definately better.

What about: Project A depends on LLBLGen LLBLGen is a dependency of Project A