![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | Project References. We've come across a problem using source control when dealing with project references and are looking to find out what the proper way of dealing with this is. When we add a reference to an assembly (in this case to ajaxcontroltoolkit.dll), it seems to put the full path to the dll in the project reference. Unfortunately as this is under the program files area, it causes problems because some developers don't have a program files area, they have a program files (x86) area instead, so the project doesn't find the assembly when they download the project it from source control. How should this be done to avoid this kind of problem? TIA. -- Adrian |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Project properties -> References error | .NET General | |||
| VB Commandline compiler references | .NET General | |||
| In any project, Can't we refer classes directly, (without addingphysically in the project)? | .NET General | |||
| Microsoft Advances Its Project Management Technology and the Project Management Profession | Vista News | |||