 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / Visual Studio.NET / General / July 2004VS.NET 2003 Project References
Hello, I have a solution with one MFC EXE project and several MFC DLL projects. No I add the DLL projects to the Refernences folder of the EXE project. I would have expected that the import libraries are added to the linker input. But this is not the case. So basically I don't see any consequences of doing so. My question now is what's the purpose of being able to add such a reference? Regards, Ralf Tobel Hi Ralf, > So basically I don't see any consequences of doing so. > > My question now is what's the purpose of being able to add such a reference? The "Add Reference" feature is mainly designed for the managed code projects(VC#, VB.NET, MC++) to add components(.NET component and COM component or the previous stuffs in projects), for adding an unmanaged DLL dependency to an unmanaged project like MFC application, you have to do it manually just as under VC6. Thanks! Best regards, Gary Chang Microsoft Online Partner Support  SignatureGet Secure! - www.microsoft.com/security This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- > The "Add Reference" feature is mainly designed for the managed code > projects(VC#, VB.NET, MC++) to add components(.NET component and COM > component or the previous stuffs in projects), for adding an unmanaged DLL > dependency to an unmanaged project like MFC application, you have to do it > manually just as under VC6. Thanks. So this means that there is no effect in doing so. I think it would be a good idea to add the import library to the linker input when adding the project to the References. In VS6 this was the case when you added a project to the dependencies of another project. Regards, Ralf It seems to be a different problem. The manual says: Ignore Import Library Tells the linker not to try to link any .lib output generated from this build into any dependent project. This allows the project system to handle .dll files that do not produce a .lib file when built. If a project is dependent on another project that produces a DLL, the project system automatically will link the .lib file produced by that child project. This may not be needed by projects that are producing COM DLLs or resource-only DLLs; these DLLs do not have any meaningful exports. If a DLL has no exports, the linker will not generate a .lib file. If no export .lib file is present on the disk, and the project system tells the linker to link with this (missing) DLL, the link will fail. So it should work like in VS6 and automatically add the import libarary of a dependent project to the linker input. Allthough this option is set to 'no' it doesn't do this. Hi >So it should work like in VS6 and automatically add the import libarary of a dependent project to the linker input. oh yes, in VS7.1 it works as the same way as VS6 if you have the VC DLL project with your main VC app's project in a same solution(you will find the "Project Dependencies..." entry in the main VC app project 's right button menu then). Thanks! Best regards, Gary Chang Microsoft Online Partner Support SignatureGet Secure! - www.microsoft.com/security This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- > oh yes, in VS7.1 it works as the same way as VS6 if you have the VC DLL > project with your main VC app's project in a same solution(you will find > the "Project Dependencies..." entry in the main VC app project 's right > button menu then). In deed, if I set up a small example solution it works. Only in our complex solution it doesn't work. I have to investigate further, thanks for your help. Regards, Ralf Hello Ralf, I was reviewing this post thread. Based on my experience, if you have detail repro steps for a complex structured solution, please post it here and we could investigate it on our side. Thanks very much. Best regards, Yanhong Huang Microsoft Community Support Get Secure! ?C www.microsoft.com/security This posting is provided "AS IS" with no warranties, and confers no rights. I have a small solution where I can reproduce it. But it's still too large to post it (The server denies it.). Can I send it an email address? Regards, Ralf OK, Ralf! just remove the word "online" of my email alias and zipped it. Thanks! Best regards, Gary Chang Microsoft Online Partner Support SignatureGet Secure! - www.microsoft.com/security This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.