Which files from the release build of visual studio 2017 should reach the end user?

Question

0.00/5 (No votes)

See more:

In Visual Studio 2017, when I build my C++ DLL (release build) I get the following list of files in the release folder:

MyLiberary.dll
MyLiberary.exp
MyLiberary.iobj
MyLiberary.ipdb
MyLiberary.lib
MyLiberary.pdb

My questions is: which of these should be sent to the end user besides the .dll file?

I think the pdb file contains symbol names and is useful for debugging (however, I have found that error messages from my released WPF app contained correct symbol names even when the pdb file was not in the folder). What about the other files?

What I have tried:

Sending all the files.........

Posted 25-Aug-17 5:50am

HD86_

Updated 25-Aug-17 6:07am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Jochen Arndt · Accepted Answer · 2017-08-25T06:07:00

Solution 1

Only the DLL file to execute an application using the DLL.

For programmer's who want to use your DLL, create a separate package with the DLL, LIB file, header file, and documentation about the exported functions. Optionally provide also a debug build (DLL and LIB file).

Posted 25-Aug-17 6:07am

Jochen Arndt