Common Languge Runtime Debugging Services
-
After creating an application in C# that runs fine on my computer and another developer's computer, we included it in an InstallShield project. When we try to run it we see the message box saying: X| Common Languge Runtime Debugging Services Application has generated an exception that could not be handled. Process id=0xb3c(2876), Thread=0xb40(2880) Click OK to terminate the application. Click CANCEL to debug the application. I've created a Release version but that didn't seem to matter. We have another program that's written in .NET that works fine. I've seen many postings on this error on the net but no solutions. Any ideas? :doh:
-
After creating an application in C# that runs fine on my computer and another developer's computer, we included it in an InstallShield project. When we try to run it we see the message box saying: X| Common Languge Runtime Debugging Services Application has generated an exception that could not be handled. Process id=0xb3c(2876), Thread=0xb40(2880) Click OK to terminate the application. Click CANCEL to debug the application. I've created a Release version but that didn't seem to matter. We have another program that's written in .NET that works fine. I've seen many postings on this error on the net but no solutions. Any ideas? :doh:
The most common thik of an error msg like this listed below (as I know): - framework not installed - some require component not installed/registered So if you use a dll or ocx you must register it, in the other machine too. eg.: from command line: regsvr32 mycomponent.ocx or regsvr32 mycomponent.dll
-
The most common thik of an error msg like this listed below (as I know): - framework not installed - some require component not installed/registered So if you use a dll or ocx you must register it, in the other machine too. eg.: from command line: regsvr32 mycomponent.ocx or regsvr32 mycomponent.dll
Actually you are close, we figured it out. My program is using an Access database via a datasource connection. When the program begins to load, it attempts to connect to the datasource. Unfortunately the connection path is hardcoded and the installation computer did not have the same directory structure. So when the program started it could not find it's datasource. We changed the path and moved the database to the right directory and it worked. Ahhhh engineering! :-D Normality is a weakness...