managed c++ app refuses to run
-
We're having a problem on a few client machines where our managed C++ MFC app will not start. Its a managed c++ app linked to some C# dlls. It won't even hit the constructor or OnInitApp. Its almost identical to this: http://www.eggheadcafe.com/community/aspnet/36/10076902/mixed-c-managed-c-c.aspx[^] but of course there was no solution posted. I have one of the offending machines and it starts in safe mode, but not when starting windows normally. I have also shutdown nearly every service, including anti-virus apps. It seems like something is blocking it but everything that possibly would be blocking it has been turned off. Tried running the CLR Profiler with the app but the clr doesn't start. Any clue's as to what is causing this would be appreciated. Thanks
"Make everything as simple as possible, but not simpler." - Albert Einstein
Jason Henderson
-
We're having a problem on a few client machines where our managed C++ MFC app will not start. Its a managed c++ app linked to some C# dlls. It won't even hit the constructor or OnInitApp. Its almost identical to this: http://www.eggheadcafe.com/community/aspnet/36/10076902/mixed-c-managed-c-c.aspx[^] but of course there was no solution posted. I have one of the offending machines and it starts in safe mode, but not when starting windows normally. I have also shutdown nearly every service, including anti-virus apps. It seems like something is blocking it but everything that possibly would be blocking it has been turned off. Tried running the CLR Profiler with the app but the clr doesn't start. Any clue's as to what is causing this would be appreciated. Thanks
"Make everything as simple as possible, but not simpler." - Albert Einstein
Jason Henderson
Jason Henderson wrote:
Tried running the CLR Profiler with the app but the clr doesn't start.
Can you run any other .NET application on this machine? If not, I guess the problem will be with the setup of .NET framework.
Best wishes, Navaneeth
-
Jason Henderson wrote:
Tried running the CLR Profiler with the app but the clr doesn't start.
Can you run any other .NET application on this machine? If not, I guess the problem will be with the setup of .NET framework.
Best wishes, Navaneeth
While looking for some tool to help I installed PerfMon which I believe is a .net app and it ran fine. All of our other native apps run fine as well.
"Make everything as simple as possible, but not simpler." - Albert Einstein
Jason Henderson
-
We're having a problem on a few client machines where our managed C++ MFC app will not start. Its a managed c++ app linked to some C# dlls. It won't even hit the constructor or OnInitApp. Its almost identical to this: http://www.eggheadcafe.com/community/aspnet/36/10076902/mixed-c-managed-c-c.aspx[^] but of course there was no solution posted. I have one of the offending machines and it starts in safe mode, but not when starting windows normally. I have also shutdown nearly every service, including anti-virus apps. It seems like something is blocking it but everything that possibly would be blocking it has been turned off. Tried running the CLR Profiler with the app but the clr doesn't start. Any clue's as to what is causing this would be appreciated. Thanks
"Make everything as simple as possible, but not simpler." - Albert Einstein
Jason Henderson
-
Sounds like you should install Microsoft Visual C++ 2008 Redistributable Package (x86)[^]
Don't be overcome by evil, but overcome evil with good
It gets installed in our software's installation script, but I reinstalled it anyway. Didn't help.
"Make everything as simple as possible, but not simpler." - Albert Einstein
Jason Henderson
-
It gets installed in our software's installation script, but I reinstalled it anyway. Didn't help.
"Make everything as simple as possible, but not simpler." - Albert Einstein
Jason Henderson
Two things may help you: 1.Use Depends(dependency walker) on the cli module. I beleive that you will find a missing environment path or a missing dll that you assumes you have. 2.Try Fusion Log - it will give you an indication of .net binding errors. Good luck, Yoav