G
Guest
If have a line of code which does a new ObjectX, but I ensure this code never
gets executed, I.e I have an if statement around it, I find that I get an
error at run time that the dll for Object X cannot be found - i.e it still
looks for its dll at run time even though this line of code is never
executed. Just checking - Is this standard behaviour with DotNet? I believe
so but just want to check.
What DotNet seems to do is resolve its references on a function by function
basis so as soon as it encounters my function with new ObjectX, it complians
that it can't find the ObjectX dll even though this line will never be
executed.
gets executed, I.e I have an if statement around it, I find that I get an
error at run time that the dll for Object X cannot be found - i.e it still
looks for its dll at run time even though this line of code is never
executed. Just checking - Is this standard behaviour with DotNet? I believe
so but just want to check.
What DotNet seems to do is resolve its references on a function by function
basis so as soon as it encounters my function with new ObjectX, it complians
that it can't find the ObjectX dll even though this line will never be
executed.