Hi!
I have recently moved to the windows server 2008.
My 32 bit com+ application used to have configuration file located at: system32 directory.
When I had copied the config file to the system32, it was copied automatically to syswow64.
I have read somewhere that an application reading system32 directory is automatically and transparently redirected
to syswow64 directory.
So here goes my questions:
1) Is it enough to copy the config file only to syswow64, should it also been copied to system32?
2) I think, that once when I copied the file to system32 it was copied to the syswow64 and deleted from system32, why?
3) Is it possible the situation that the config file was _only_ in syswow64, and the com+ application could have occasionally
problems reading the file, from system32 path?
Thanks for help in advance!
I have recently moved to the windows server 2008.
My 32 bit com+ application used to have configuration file located at: system32 directory.
When I had copied the config file to the system32, it was copied automatically to syswow64.
I have read somewhere that an application reading system32 directory is automatically and transparently redirected
to syswow64 directory.
So here goes my questions:
1) Is it enough to copy the config file only to syswow64, should it also been copied to system32?
2) I think, that once when I copied the file to system32 it was copied to the syswow64 and deleted from system32, why?
3) Is it possible the situation that the config file was _only_ in syswow64, and the com+ application could have occasionally
problems reading the file, from system32 path?
Thanks for help in advance!