As stated in the title i have that strange behaviour with the subsequent call
Assembly.GetExecutingAssembly().GetName().Name
My exe name is CoreService.exe, with the call above i get different response every time i call it eg :
- Coreservice.exe
- CoreService.exe
- CoreService.Exe
- Coreservice.Exe
- Coreservice.EXE
- CoreService.EXE
I get this behaviour working on Windows Server 2012 and only when i start my CoreService as windows service instead of windows process, anybody can explain why of that strange thing ?
Aucun commentaire:
Enregistrer un commentaire