Getting a .NET application to work on Vista
-
I have tried my application on Vista. it installs without any problem but whenever I try to run it I get this error message "APD.exe has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available" My application is developed in C# and .NET framework 2.0 . it works fine on Windows XP so what is the solution to this problem?
-
I have tried my application on Vista. it installs without any problem but whenever I try to run it I get this error message "APD.exe has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available" My application is developed in C# and .NET framework 2.0 . it works fine on Windows XP so what is the solution to this problem?
In your solution did you set it to allow later versions of .Net? As far as I understand Vista comes with .Net 3 and if you restrict your application (there is a little tick box in the setup project) to .Net 2 your application will not work.
You always pass failure on the way to success.
-
In your solution did you set it to allow later versions of .Net? As far as I understand Vista comes with .Net 3 and if you restrict your application (there is a little tick box in the setup project) to .Net 2 your application will not work.
You always pass failure on the way to success.
.NET 3 is an adjunct to .NET 2. In other words, Vista comes with 2 as well as 3 because 3 cannot exist without 2. I suspect the issue is more to do with the application violating things that Vista has locked down. It's possibly a file access issue.
Deja View - the feeling that you've seen this post before.
-
I have tried my application on Vista. it installs without any problem but whenever I try to run it I get this error message "APD.exe has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available" My application is developed in C# and .NET framework 2.0 . it works fine on Windows XP so what is the solution to this problem?
Have you tried debugging your app under Vista? You have given very little information; I don't see how this can help us help you.
Cheers, Vikram.
Zeppelin's law: In any Soapbox discussion involving Stan Shannon, the probability of the term "leftist" or "Marxist" appearing approaches 1 monotonically. Harris' addendum: I think you meant "monotonously". Martin's second addendum: Jeffersonian... I think that should at least get a mention.
-
I have tried my application on Vista. it installs without any problem but whenever I try to run it I get this error message "APD.exe has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available" My application is developed in C# and .NET framework 2.0 . it works fine on Windows XP so what is the solution to this problem?
-
I have tried my application on Vista. it installs without any problem but whenever I try to run it I get this error message "APD.exe has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available" My application is developed in C# and .NET framework 2.0 . it works fine on Windows XP so what is the solution to this problem?
What does the app do when it starts up? If you're trying to access certain parts of the registry, event logs, or certain disk folders you can see this type of behavior. You will need to run the application under a debugger to see what is happening.
Scott. —In just two days, tomorrow will be yesterday. —Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai
[Forum Guidelines] [Articles] [Blog]
-
.NET 3 is an adjunct to .NET 2. In other words, Vista comes with 2 as well as 3 because 3 cannot exist without 2. I suspect the issue is more to do with the application violating things that Vista has locked down. It's possibly a file access issue.
Deja View - the feeling that you've seen this post before.
What I was referring to is when you create a setup project, within the Launch Condition Properties there is a property called AllowLaterVersions. If this is set to false then if the application is compiled in a .Net 2 environment the installation will not work on a machine with .Net 3 present. This was an issue I experienced with a user having 3 on their machine - I changed this setting and it solved the issue. It's kinda crazy really - why would you not want an application compiled in .Net 2 to to run in 3?
You always pass failure on the way to success.
modified on Wednesday, March 26, 2008 11:03 AM
-
What I was referring to is when you create a setup project, within the Launch Condition Properties there is a property called AllowLaterVersions. If this is set to false then if the application is compiled in a .Net 2 environment the installation will not work on a machine with .Net 3 present. This was an issue I experienced with a user having 3 on their machine - I changed this setting and it solved the issue. It's kinda crazy really - why would you not want an application compiled in .Net 2 to to run in 3?
You always pass failure on the way to success.
modified on Wednesday, March 26, 2008 11:03 AM
This gets into the cluster cthulu of .net framework versioning. Going from 1 to 1.1 to 2.0 could cause problems if your application's functionality was dependent on a bug in the old version (either explictly :wtf:, or because your workaround for it didn't check for the original bug being fixed :doh:). Now we fastward a few years and for 3.0 and 3.5 the meaning changes completely from modification of old stuff to addition of new stuff only. :doh: :doh: :doh: :doh:
Otherwise [Microsoft is] toast in the long term no matter how much money they've got. They would be already if the Linux community didn't have it's head so firmly up it's own command line buffer that it looks like taking 15 years to find the desktop. -- Matthew Faithfull