Is there a way to copy the XML file of a DLL to the output directory of any application that will use that DLL

Question

0.00/5 (No votes)

See more:

I have a class library project which has a .xml file. It's property is set to "Copy Always" to "Output Directory". After building the project the file is getting copied to the output directory.

but when I'm using this dll in other applications,the .xml file is not being copied to their output directories.

How can I do that?

What I have tried:

the file is set to "Copy Always" to "Output Directory".

Posted 31-Aug-16 21:15pm

Member 12704287

Updated 13-Dec-21 20:26pm

v2

Add a Solution

Comments

Richard MacCutchan 1-Sep-16 3:26am

You need to change the properties of the file in your project.

Member 12704287 1-Sep-16 3:49am

can you explain what to change in the property?

Richard MacCutchan 1-Sep-16 4:09am

You already know what: Copy Always

Member 12704287 1-Sep-16 4:17am

I've already done that. It didn't work

Richard MacCutchan 1-Sep-16 4:55am

Sorry, but if you want help here you need to provide proper details of your problem. We have no way of guessing where your files are or what you are doing.

Member 12704287 1-Sep-16 5:06am

when I'm compiling the class library project it is copying the xml file to it's bin\debug. But when I'm using the dll in other application, the xml is not being copied in that application's bin\debug.
I want to know if there is any way to do that. i.e to set something in the class library project so the xml will be copied in the application's bin\debug.

Richard MacCutchan 1-Sep-16 5:12am

If by "using the DLL", you mean the second application is linking to that DLL then it will have no knowledge of the XML file. I do not know what your project is supposed to do, but it seems a very odd design to have a DLL dependent on an external XML file.

Member 12704287 1-Sep-16 5:21am

So you are saying it is not possible.
ok thank you.

Richard MacCutchan 1-Sep-16 5:30am

No that's not at all what I said. I merely questioned what you are trying to do. Most things are possible in software development but some are more difficult than others.

Maciej Los 1-Sep-16 3:34am

Have you seen that: Can't get Copy Always to copy to test "output directory"[^]?

Member 12704287 1-Sep-16 3:48am

can't we do anything to the dll project so that it will automatically copy the xml file to the other application's output directory?

2 solutions

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)

Bernhard Hiller · Answer 1 · 2016-08-31T22:16:00

Solution 1

Also set the Build Action to Content.

Posted 31-Aug-16 22:16pm

Bernhard Hiller

Comments

Member 12704287 1-Sep-16 4:24am

It is set to Content already

Member 13202792 · Answer 2 · 2021-12-13T20:26:00

Solution 2

you can use the post build if you are using VS, you can add a post build event like

xcopy "$(ProjectDir)Views\ModuleAHome\Index.xml" "$(SolutionDir)MEFMVCPOC\Views\ModuleAHome\" /Y /I

Posted 13-Dec-21 20:26pm

Member 13202792

Comments

Richard Deeming 14-Dec-21 5:11am

Read the question and comments again. It's not a problem when the project is built; it's a problem when the compiled output of the project is referenced in another project.

The OP doesn't seem to have been back in the five years since they asked this question, so either they found a solution or workaround, or they gave up.