updated dll version is not getting in installer

Question

1.00/5 (1 vote)

See more:

VS2008

, +

Hi,

i have a wpf project , in that i am using a dll called test.dll. i created the setup and installed in my system. its working. then i changed some code inside the dll and referenced the updated dll in my project. the created the installer and installed in my system. but the changes in the dll is not getting in installed program. how can i get that?

i am using vsual studio installer in setup and deployment. i am using vs2010

anybody help me

thanks and regarsds
Kunjammu

Posted 27-May-14 19:36pm

Kunjammu

Updated 27-May-14 20:52pm

v3

Add a Solution

Comments

Sergey Alexandrovich Kryukov 28-May-14 2:00am

How anyone can help you having virtually no information? There can be too many ways to screw up things. We don't even know what installation toolset you are using. And WPF is irrelevant.
—SA

Kunjammu 28-May-14 2:44am

i am using vsual studio installer in setup and deployment. i am using vs2010

Sergey Alexandrovich Kryukov 28-May-14 3:00am

Here we go again: How anyone can help you having virtually no information? The only thing we know that you are using VS 2010 Setup project type... :-)

By the way, this project type is deprecated, has been removed from later versions of VS and is not truly legitimate. I recommend open source WiX, which strictly follows the standards of MSBuild projects and offers decent VS integration.

—SA

Sergey Alexandrovich Kryukov 28-May-14 11:43am

After some thinking: I don't think that the problem is in the setup project. Rather, it is in the project dependencies or wrong method of the build. You just created some mess with your files. If the setup project picks up some PE file, it will be updated in setup if the file is really rebuilt. The setup build simply cannot get different versions somewhere. But if you have different copies of the same executable file somewhere, you could easily make a mistake.
—SA

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)

Sergey Alexandrovich Kryukov · Answer 1 · 2014-05-28T06:01:00

Please see my comment to the question. Your setup project cannot be a source of the problem. You just need to create your solution accurately.

Do the following: remove all temporary files and all output files from the project directories. Put all projects in the same solution, if you haven't done it before. Now, fix project dependencies in Visual Studio: make your setup project depending on projects producing PE files and other output used by the installer.

Remove everything which is not source code. You can simply look at the "output path" parameters of all your project and remove all those directories. Also remove all "obj" directories. In other words, rebuild your solution really from the source code, remove all intermediate and output artifacts. Always know what is source code and what not and always store only the source code. Never work without some Revision Control System (this is a big separate topic).

And one extra advice: after everything is done, modify the output directories of all projects for all configurations in the following way the merge all output in the same directories (one directory per configuration but the same for different projects). This way, you will avoid multiple copies of the same output files. The question could be: why Visual Studio makes different output directories? Because it does not "know" your intention. It makes many separate output directories and many multiple copies just because this is a way to make everything working in first place. Get rid of those multiple copies.

—SA

Kunjammu · Answer 2 · 2014-05-28T20:07:00

Solution 2

i changes the version of dll ans created setup, the its ok

Posted 28-May-14 20:07pm