[RESOLVED] Issue with the Dll

Hi ,
I have created the Dll for my functionality.

Now the client given me the test harness and i added my dll into that . But there is no luck, it says that the
fatal error LNK1107: invalid or corrupt file: cannot read at

But then i added the visual studio project created within the Dll into the test harness solution and also copied my files in the same folder. Then compiled the test harness soliution. Then I could see the dlll getting loaded properly.
There is a call within the test harness like dll->GetPropModel(). I can see the My dll is getting called when i put the breakpoint at this point.

It is frustrating. That now all the functionality is tested with this method. And finally i cannot deliver my code to client as it is not recognising my Dll individually.

My code has some has some lib and tlb files. Does it package under the same dll or is it because of this i cannot packahge my code under one dll.

Thanks
Pdk

Well, you are alone with this error: https://www.google.com/search?q=LNK1...hrome&ie=UTF-8
Did you read how the others tried to solve this problem?

LNK1107 usually means that you are trying to link to a .dll file instead of a .lib file. When a .dll file is compiled the .lib file will also be generated. This is the file that is used to link - not the .dll file.

Quote:

---

Originally Posted by 2kaud

LNK1107 usually means that you are trying to link to a .dll file instead of a .lib file. When a .dll file is compiled the .lib file will also be generated. This is the file that is used to link - not the .dll file.

---

Thanks a lot kaud. I was adding the .dll under Project->Configuration Properties->Linker->Input->Additional Dependencies.
Now changed to .lib and everything works like magic. My big big headache is gone.
Thanks a lot kaud. Much appreciated.

Say, as an aside, do you realize you can debug the dll by setting the path to the exe that loads your dll?

In VC 2019 (previous versions are similar):
Right click on the dll project and choose properties.
Click on the Debugging node under Configuration Properties.
Change the Command property to point to the exe that loads the dll.
When you debug, the exe will start which loads your dll.

Thanks a lot Arjay, will try this