At first, I thought this was going to be an alternative way of specifying
what assemblies are tied in to your project. IE, instead of putting in
individual "References" via the right-click, Add Reference, you could just
put in the name of a folder containing dependent assemblies and it would go
look there at compile time and link them in. But, of course that doesn't
work... The documentation only tells you how to add or remove paths from the
list but it doesn't explain what impact those settings have on your project.
So, what does that setting really do?
Thanks,
Chris
"Gary Chang[MSFT]" - 31 May 2006 07:55 GMT
Hi Chris,
Thank you posting!
>So, what does that setting really do?
The Reference Path setting is used for the VS2005 compiler to search the
specified path if the project's references a private assembly is not in the
project directory. If the current projects reference link is valid, the VS
IDE will not using this setting.
For example the VS2005 will use the relative path for a private assembly
you referenced in your project. If you remove your project to another
directory, that original relative path will not work. In this scenario, the
VS IDE will use the Reference Path setting to resolve that private
assembly's reference.
Thanks!
Best regards,
Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.