L
Lady_A
I got an application with an html,css and js UI.
The UI basically creates an ActiveX object, which is an unmanaged C++ COM
dll which in his turn creates other COM C++ dlls and C# assemblies.
At some point there is the reading of some XML files and the loading of
localized resources.
The result of all this is a localized dialog presented to the user.
All of this works great on every platform and language besides one specific
model of machine manufacturer and the Chinese language OS installed on that
machine where getting to the dialog takes 13 minutes. Perhaps on another non
English OS it doesn't work as well.
I had no resources to investigate that.
The behavior also only appears on the first try. If I close the application
and launch it again everything is great.
In order to reproduce the problem I need to reinstall the application.
While I am reinstalling the app to reproduce the problem again and I need to
reboot.
A cmd line window is hanging (and can not be terminated by the OS), which
appears to be running the csc.exe file from the Microsoft.net framework
folders. The description of the file indicates that this is a C# compiler
(?!). Obviously I did not run it.
After a couple of reinstallations the problem disappears at all and the only
thing that brings it back is restoring the machine's image.
I did try another machine of the same model and manufacturer and it happens
on both.
Once I exchange the dlls with the same ones, compiled on a different machine
than the original ones, where the only differences is the addition of
message boxes, to tell me at what stage are we now, it works well.
I tried to exchange the resource dlls with a previous version, exchanging
that ActiveX dll with a previous version, installing msxml4 for those XML
files.
Tried to apply .net framework 1.1 sp1, Microsoft hotfix.
Nothing helps.
It seems like a .net problem since the code doesn't change from the first
launch of the app to the second and that hanging c# compiler is disturbing.
I guess something is being configured and remembered since on the second
launch I got no hang.
What could be those settings that are remembered ?
Any specific sources I can read up on what could those remembered settings
be ?
Anything leads would help!!!
Thank you!!!
The UI basically creates an ActiveX object, which is an unmanaged C++ COM
dll which in his turn creates other COM C++ dlls and C# assemblies.
At some point there is the reading of some XML files and the loading of
localized resources.
The result of all this is a localized dialog presented to the user.
All of this works great on every platform and language besides one specific
model of machine manufacturer and the Chinese language OS installed on that
machine where getting to the dialog takes 13 minutes. Perhaps on another non
English OS it doesn't work as well.
I had no resources to investigate that.
The behavior also only appears on the first try. If I close the application
and launch it again everything is great.
In order to reproduce the problem I need to reinstall the application.
While I am reinstalling the app to reproduce the problem again and I need to
reboot.
A cmd line window is hanging (and can not be terminated by the OS), which
appears to be running the csc.exe file from the Microsoft.net framework
folders. The description of the file indicates that this is a C# compiler
(?!). Obviously I did not run it.
After a couple of reinstallations the problem disappears at all and the only
thing that brings it back is restoring the machine's image.
I did try another machine of the same model and manufacturer and it happens
on both.
Once I exchange the dlls with the same ones, compiled on a different machine
than the original ones, where the only differences is the addition of
message boxes, to tell me at what stage are we now, it works well.
I tried to exchange the resource dlls with a previous version, exchanging
that ActiveX dll with a previous version, installing msxml4 for those XML
files.
Tried to apply .net framework 1.1 sp1, Microsoft hotfix.
Nothing helps.
It seems like a .net problem since the code doesn't change from the first
launch of the app to the second and that hanging c# compiler is disturbing.
I guess something is being configured and remembered since on the second
launch I got no hang.
What could be those settings that are remembered ?
Any specific sources I can read up on what could those remembered settings
be ?
Anything leads would help!!!
Thank you!!!