Have Geek Brain

.NET 2.0 (VS 2005) works in Visual Studio but not Windows Explorer

Has anyone seen this?

There is a few seconds of delay, then one of these dialog boxes that says "Yada Yada has encountered a problem and needs to close. We are sorry for the inconvenience." (This is strange because my program has an exceptional handling system that gives helpful error messages if an exception is thrown in my code, but clearly does not reach that point: this dialog is the same as what you see if you try to run. NET program on a computer without .NET installed.) This same binary works on other Windows systems.

I tried reinstalling .NET 2.0. I tried to remove it (do not allow). I tried "Change" it (nothing changes). I tried to republish my project (ClickOnce) and it still works on other machines, but not on my development machine other than Visual Studio. I tried to uninstall the installed ClickOnce project and reinstall, but it still won't start the program.

The closest I found was this (read its Clarification), but none of these solutions worked.

I am considering renaming the program and republishing and reinstalling to see if it has to do with the mysterious GAC or the evil case, but.

+1


a source to share


6 answers


Check the application event log using Event Viewer. You probably won't get a lot of information, but sometimes you can point you in the right direction.



+1


a source


Do you have anything that catches and reports unhandled exceptions in the event section of the application?



+1


a source


I also suggest making a manual copy of the EXE and Dlls to the directory and get yourself a copy of Reflector and open the main exe app with reflector and then go through all the links. Maybe there is some kind of dependency where it expects a different version or something in Gac that is older and you thought you removed it.

Also find the entry point in your program and see what Reflector thinks.

+1


a source


Have you tried redistributing (vcredist_x86.exe)?

0


a source


Have you tried manually copying the exe and support files to the machine instead of using publish? Also, you don't want you to run into a problem, but on our machine, which sometimes has such a problem, we have a copy of Visual Studio, so it offers a debug or private hint, we remove the debug and copy the source it asks for and we will get more details.

0


a source


Does it fail to run when you double click on the output of your compiler? If so, what usually solves it for me is specifying Copy Local = True for all DLLs mentioned in the project.

0


a source






More articles:


All Articles