Information générale
Catégorie:
Codage, syntaxe et commandes
Versions des environnements
Network:
Windows Server 2008 R2
Virtual environment:
VMWare
Update: figured out that this comdlg32.ocx now needs to be in syswow64. But cannot use copy command to COPY (lcSource) TO (lcTarget) to copy it into this directory (probably because it is a system directory). If you do it manually via file explorer, you get a dialog asking if you want to continue (assuming you have enough rights).
Am I going to have to use some other process to copy this file into place (perhaps a powershell script with elevated rights - which I have no idea how to write) or will their IT help desk have to install and register this manually on all their PC's?
Albert
>Hi all,
>
>Used the comdlg32.ocx in an app to allow the user to multi-select files. To automate the setup for the user, I had a utility that checked for this file in their windows\system32 directory and if not found, copy it in and register it. This now fails under Windows 10. Have read some forums and want to confirm:
>
>- should it still go in \system32 or should it now be in syswow64?
>- should the regsvr32 call be from system32 or syswow64 (I have not checked this yet so not sure...wanted to throw this up here before leaving for the night).
>
>I noticed there is a more recent comdlg32.DLL in system32 now (the .ocx was 1999 vintage) but did not really want to have to figure out how to setup and call that (unless someone has used it and has some quick code for me to convert to that).
>
>Thanks,
>Albert
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement