cannot run the wpf application after installing ?

Question

2.00/5 (2 votes)

See more:

VS2010

Hello all,
I have a project that have two projects One control library and main project . It is working in Vs but after installing it not working..

I place the All .dll in one folder and Exe in other folder ,
like :

Program Files\MyApp\dll\

Program Files\MyApp\exe\

now it not working Why ???????
any problem in this stretcher of Setup project ..
attaching a link to sample project link : Sample project
(https://skydrive.live.com/redir?resid=D54B0993343A8868!133&authkey=!ACZ_YFWN08UQQlU[^])

VB

with regards ,
jophy

Posted 10-Jul-12 6:24am

jophyjob

Updated 10-Jul-12 20:19pm

v2

Add a Solution

Comments

[no name] 10-Jul-12 12:39pm

"any problem in this stretcher".. not sure at all what that is supposed to mean. Is Program Files\MyApp\dll in the system path? Are you getting an error when you run your project? Does the process show up in task manager? Is your exe and dll supposed to be seperated into different folders?

Sergey Alexandrovich Kryukov 10-Jul-12 13:23pm

Not enough information.
--SA

Trak4Net 10-Jul-12 13:36pm

Have a look at this...
http://msdn.microsoft.com/en-us/library/7d83bc18(v=vs.80).aspx

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)

Dave Kreskowiak · Answer 1 · 2012-07-10T08:12:00

Solution 2

The quick solution is to NOT seperate your .DLL files from the .EXE. Put them all in the same folder.

When a .DLL is needed the assembly resolver will look in the same folder as the .EXE calling for it (by default, it will NOT look in subfolders!) If it is not there, it'll start walking the PATH environment variable looking for it.

The long answer is to tell the assembly resolver where to probe for .DLLs (assemblies). You put this in your applications initialization code:

AppDomain.CurrentDomain.SetupInformation.PrivateBinPath = "mySubFolderName";

The specified sub folder MUST be a subfolder under the .EXE launch folder for this to work:

C:\Program Files
    myCompanyName
        myApplicationName         <-- your .EXE goes in here
            DLLs                  <-- your .DLLs go here

Posted 10-Jul-12 8:12am

Dave Kreskowiak

Updated 10-Jul-12 8:13am

v2

Comments

jophyjob 11-Jul-12 0:07am

It not working ... i getting error dll not found , my need is that make exe without dlls( embedded dll in side exe) i added a link to sample project see link

Dave Kreskowiak 11-Jul-12 8:18am

Well, THAT completely changes the question.

So long as all the .DLL's are .NET .DLL's you can use ILMERGE (http://www.microsoft.com/en-us/download/details.aspx?id=17630) to combine the assemblies into one.

jophyjob 11-Jul-12 9:40am

I am using Wpf application is it possible o use ILMERGE. I also using DevExpress dlls any problem

Sergey Alexandrovich Kryukov 11-Jul-12 14:42pm

WPF should not make any difference.
--SA

Dave Kreskowiak 11-Jul-12 19:24pm

How about this.... TRY IT!

Sergey Alexandrovich Kryukov 11-Jul-12 14:41pm

Well, this is a right idea, my 5.
I should only add that using the depending .NET assemblies in different directories is quite possible and practical if one shared some assemblies in several applications. In this case, the developer should take care about the assembly location resolution. It can be done with *.exe.config files...
--SA

Sergey Alexandrovich Kryukov · Answer 2 · 2012-07-10T07:49:00

In the description of this issue, there is no information we could use to help you. You can make some of the following steps:

Make sure you do not use any hard-coded path names in the project. There are no situations when it can be helpful. All the path names should be calculated during run-time based of data, such as: 1) location of the entry assembly main executable module like "\MyApp\exe\", 2) "special directories" in the data area reserved for all users or per user, returned by System.Environment.GetFolderPath(Environment.SpecialFolder) (see http://msdn.microsoft.com/en-us/library/14tx8hby.aspx[^], http://msdn.microsoft.com/en-us/library/system.environment.specialfolder.aspx[^]), 3) defined by the data of configuration file(s), 4) obtained from user input.
Catch all exceptions in the top of the stack of every thread and output comprehensive exception information, including Exception.Stack and all Exception.InnnerException, recursively. Of course, you should make sure that you do not block exception propagation in between; this is a big mistake many beginners do; the best exception handling, as a rule of thumb, is not catching any exceptions except on top of the stack; another place is the main event loop of the UI.

Please see my past answers on exception handling for more ideas:
How do i make a loop that will stop when a scrollbar reaches the bottom[^],
When i run an application an exception is caught how to handle this?[^],
throw . .then ... rethrowing[^],
Error Logging and Screen Shot.[^],
Catching an Exception[^],
Handling exceptions in class library (dll)[^].
Add logging to check up if the code passes all points of your application logic. Use System.Diagnostics.EventLog. Please see:
http://msdn.microsoft.com/en-us/library/system.diagnostics.eventlog.aspx[^].
You can also run the application using the debugger, but this time, in place of installation. In you development code, change the output path to make is the same as the installation path for the executable module. Build the code; now your code will replace the installed code while keeping all your installed options intact. Debug the code.

Good luck,

—SA