We Keep Coding

Enterprise Architect add-in .dll crashes when deployed on to a Windows 7 machine

I have created a C# add-in in VS2015 to import and synchronise data models from Power Designer into Enterprise Architect. It has dependencies for PDPDM, PDLDM, PDCDM, and Interop.EA.
The problem is that it crashes when I deploy and then run it on a Windows 7 Machine.
To install the add-in I do the following:
Register the add-in dll in the COM codebase entries in the registry using regasm.exe
By opening up a command prompt in folder where you copied the add-in dll and register the dll with the /codebase option. In my case that command would be: %WINDIR%\Microsoft.NET\Framework\v4.0.30319
.\RegAsm.exe -tlb -codebase
Add the registry key: Add a key to HKEY_CURRENT_USER\Software\Sparx Systems\EAAddins in the form of [ProjectName].[ClassName]
This installation works fine on both the development and deployed machines and I am able to run the add-in.
The add-in works completely fine when installed on the development machine.
However on the deployed Windows 7 machine it crashes in one specific case:
When running an import for a physical data model the add-in starts working (starts to extract Power Designer information) and then crashes unexpectedly with only the message that it Enterprise Architect has "stopped working". In the event log the information points to the .NET clr.
This is unexpected as the add-in was registered with the same version of .NET in both cases.
I have investigated source code and compared it to a working dll made using the same libraries and found no differences. I am sure it is to do with the deployment environment on the Windows 7 machine.
Any ideas on why the add-in might be crashing on the Windows 7 machine?
And any suggested fixes?
UPDATE: I have tried narrowing down and commenting out aspects of the code to make it work on the Windows 7 machine. No matter what I comment out as it starts reading any part of the Physical Model from power designer it crashes, this is not the case for all other data models (logical and conceptual).
Given the way it is behaving I am looking further into the environment and deployment.
Any help is still much appreciated...
UPDATE 2: Thank you for the help from everyone. I have used the advice and was able to eventually track down the error:
The process was terminated due to an internal error in the .NET Runtime at IP... with exit code 80131506.
I am pursuing this error code and errors with the environment/garbage collector

The problem was as Geert suspected, with Power Designer. The Power Designer type libraries used were different between machines with one patch to Power Designer upgrading the PdPDM type library to a new version. This changed the way Physical Data Models interacted with the add-in when using the PdPDM type library.
It may be helpful to note that creating and using a dump file when an enterprise architect add-in crashes was very helpful and pointed me to lines of code that could isolate the problem.

Crystal Report in .NET Framework 4.0

We've a WPF application written in .NET 3.5 using Visual Studio 2010. The solution consists of 8 projects - all compiled in .NET 3.5. The application uses Crystal Report. Target OS is Windows 7.
Recently, the startup project is compiled in .NET 4.0 due to some 3rd party DLL dependency - those DLLs require .NET 4.0. After this change and rebuilding the solution, Crystal Report is throwing exception.
The problem occurs at the constructor of ReportClass.
Exception's message:
The type initializer for
'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an
exception.
InnerException's message:
"Retrieving the COM class factory for component with CLSID
{4DB2E2BB-78E6-4AEA-BEFB-FDAAB610FD1B} failed due to the following
error: 80040154 Class not registered (Exception from HRESULT:
0x80040154 (REGDB_E_CLASSNOTREG))."
I haven't worked in Crystal Report before. What could be the cause of this problem?
Please note that this problem doesn't occur when compiled as .NET 3.5. Crystal Report is used in the startup project.

It is likely to be X86/x64 problem.
try to compile your app to target 86 platform.

This issue got me for 2 days and its all over the place with very similar answers, however what it ended up being for me was two-fold. I am adding here in hopes it saves someone at least a day..
A lot of post mention this;
Go to IIS -> application pools -> click right button on your application pools -> go to advance setting -> Enable 32 bit application = True
Please note that in my case I was building and deploying on a 64bit machine so I set the True to False and it did it. Again, simple enough but not something I thought was related so my mind was blank to it after I made the adjustment.
The other point of interest is to make sure that you do have the CRRuntime_xx.x.x.MSI loaded on Deployment server.
Thank you everyone here for the amazing info at the end of the day it got me through.

Go to IIS -> application pools ->click right button on your application pools -> go to advance setting -> Enable 32 bit application = True

When you install CR it should install few files (JS,html etc etc) on C:\inetpub\wwwroot\aspnet_client\system_web\4_0_30319\crystalreportviewers13. Check if this folder exists on your pc. If not, I think you need to copy the folder from program files to this location.

These answers got us to the right place but not until we did some troubleshooting. It did end up being a 32/64 bit issue on our local dev machines running Visual Studio 2019 and IIS Express.
In our case the issue was that the setting for "Use the 64 bit version of IIS Express for web sites and projects" had been enabled in visual studio settings. We use the 32 bit version of crystal on our dev machines so we had to Uncheck this box for it to work correctly.

.NET 4 Program written/compiled on Windows 7 machine won't run on XP

I have an app that I wrote using C# .NET 4.0 in Visual Studio 2010 on my Windows 7 Ultimate machine. This app works fine on both Vista and other Windows 7 computers, but whenever someone running Windows XP tries to run it it crashes.
In order to reproduce this I've tried running it on my Win XP VMWare machine and it crashes for me in there. Unfortunately it doesn't give me any specific error, just informing me that the program has crashed and needs to close.
One other user sent me the following:
Run-time error '339'
Component 'vbalSGrid6.ocx' or one of its dependencies not correctly registered: a file is missing or invalid.
Code 0xe0434352
Flags 0x00000001
I don't get that particular bit when I try to run it on my Virtual XP machine, and I also made sure to install .NET 4.0 on there.
What could be causing this, and why won't the app run in XP if the .NET 4 framework is supported for XP?
Components used in the program: DataGridView, ComboBox, Buttons, Labels, LinkLabel, NewtonSoft's JSON parser, and that's about it.
I am baffled and have utterly no idea where to start. Ideas?
UPDATE: Hmm, tried running my other recently created application on XP and it loaded fine. The only major difference (in the components I used anyway) between the two is my use of NewtonSoft's JSON library, which I actually think is a .NET 3.5 component.
UPDATE 2: Just for kicks I tried running the program on my Wind7 machine in "Windows XP SP3" compatibility mode and it ran fine. Of course, I have no idea just how closely the "compatibility mode" emulates a true XP SP3 environment, but I figured I'd give ya'll the info anyway.

¡¡ IT WAS THE APPLICATION ICON !!
I kept noticing that the module it referenced in the error it gave me was system.drawing which I thought was odd. I figured perhaps the PictureBox I was using was causing the issue, so I tried disabling everything to do with that, to no avail.
I had my business partner set up his XP box so that we'd have another machine to test with aside from my VMWare XP box just in case there was some odd issue with it.
After he got it set up and the app copied over he said "The icons look like DOS ones" and I had a eureka moment.
I was using .PNG's as the icons because they support transparencies and whatnot, but XP doens't natively support them. So when the app was copied to the desktop it just used a generic icon for it, and when the application was run it crashed because XP doesn't know how to render a .PNG.

Try using the Fusion Log Viewer to debug startup errors in .NET applications.
Scott Hanselman has written a nice howto along with links to further resources if you need to go deeper.

Are we sure this is some wierd .NET compatibility issue or just a run of the mill bad installer/deployment problem?
Here's one user who has that error message because the OCX DLL was copied to System32 with a shortname. Renaming the DLL to the correct name and running RegSvr32 resolved his problem.
Do you have an installer? Have you correctly identified all of your managed and unmanaged dependencies and properly authored them into your installer?
http://forums.elmsoftware.com/forum_posts.asp?TID=119

DevExpress - windows forms application1 has encountered a problem and needs to close?

I've playing around with DevExpress gauges. Works fine on my computer, yet when I build the .exe file and give it to someone, his computer shows "windows forms application1 has encountered a problem and needs to close".
Any ideas what might be causing it?
Thanks!

There's a variety of reasons why this could be happening.
1) .NET framework isn't installed correctly or the version you developed the application does not match the end machine .NET version.
2) DevExpress puts the assemblies on your Global Assembly Cache. The application running on the end machine must a way to find these assemblies.
In this case you have 2 choices:
Place the DevExpress DLLs you are referencing in the same directory the application is running (recommended)
Install DevExpress / Copy the DLLs to GAC on the end machine

C# app runs in Windows 7, but not in Windows XP

I have created an application in VS C# Express 2008 using Windows 7 as my OS. It runs perfectly fine on other W7 machines, but when we try and deploy it on a machine with XP it doesn't even run. I just get the usual "Application needs to be terminated" error message. The app was built using .NET 3.5 and all the machines have at least 3.5 installed. Is there anything that I may be able to do to get the program running in previous versions? Thanks in advance for your help.
Updated Info. The machines all use x86 32-bit OS, either XP SP3 or W7, so I don't think that there is a huge need for checks for 64-bit issues. The application itself is loading images into an image list and adding in an image when it finds a break in the file names. (eg. There are 4 images in a folder, 1-3 and 5, what the application does is iterates through each image name and the minute it sees that image 4 is missing, it adds a placeholder image and labels it image 4.)

You should set up an UnhandledExceptionEventHandler so that you can log information about the current state of your application and the exception information. It isn't going to stop your application from crashing, but it will give you more information about what happened and make it easier on your end user to give you what you need to know when the application crashes.
This article give a good description of how to do that.

First you must be sure that .Net Framework 3.5 is installed on your Windows XP machine. If everything is OK, then you should check if you are using "3rd party dlls as reference" and validate their existence and correct versions on your Windows XP machine.
Probably this can help.

Log the exception which is thrown by the application so that you can fix it.

Not a lot of info but some things to check:
Make sure you have the latest patches on XP and SP release
Maybe you need to run the program as administrator - are you logging in as admin
Have you checked the windows appliation error log to see if there is anything there that might be helpful