Our application is a Win32 hybrid unmanaged application and a .NET 2.0 managed application. The Win32 part is the main executable file, which at some point downloads and hosts the .NET 2.0 runtime and loads some managed modules to open new winforms.
We had our share of problems like CASPOL, but today we have a very strange problem, and I hope someone can give me some pointers or ideas, or basically something really that will spark something that will help us solve this problem.
On a server accessed via citrix, if the application files are located in a directory located on the desktop of the current user, who is the server / domain administrator, the program works fine. .NET windows open as expected.
However, if we move the directory to the root of the same drive, which is the physical drive on the server (so there is no SAN mapping and nothing that could trigger the CASPOL command, as far as I know) and keep everything else the same, the same user, the same configuration, etc., the application crashes silently when we try to call .NET windows. It crashes, just disappearing, which suggests that it could be something like. We are studying adding registrations to some parts of the application so that we may be able to figure out what is happening and where, but I also post this question.
So far, we have verified that there are no oddities in the CASPOL access list, there is nothing strange in the NGEN cache (I thought that there were damaged images before if the server owner played with it), and there is no oddity in the GAC (we do not use the GAC for assemblies )
:
- U:\Documents and Settings\USERNAME\Desktop \,
- U: \,
- U:
- NGEN GAC
- .NET, ( , )
- - ?
: / "".