handles

问题 Assuming I already have the handle to a window, I can get the PID with GetWindowThreadProcessId . Is there a way I can get the process name without having to get all the processes and try to match my PID? 回答1: You can use Process.GetProcessById to get Process . Process has a lot of information about the running program. Process.ProcessName gives you the name, Process.MainModule.FileName gives you the name of the executable file. 回答2: Process.GetProcessById(id).ProcessName 回答3: // Here is a

问题 Assuming I already have the handle to a window, I can get the PID with GetWindowThreadProcessId . Is there a way I can get the process name without having to get all the processes and try to match my PID? 回答1: You can use Process.GetProcessById to get Process . Process has a lot of information about the running program. Process.ProcessName gives you the name, Process.MainModule.FileName gives you the name of the executable file. 回答2: Process.GetProcessById(id).ProcessName 回答3: // Here is a

问题 Assuming I already have the handle to a window, I can get the PID with GetWindowThreadProcessId . Is there a way I can get the process name without having to get all the processes and try to match my PID? 回答1: You can use Process.GetProcessById to get Process . Process has a lot of information about the running program. Process.ProcessName gives you the name, Process.MainModule.FileName gives you the name of the executable file. 回答2: Process.GetProcessById(id).ProcessName 回答3: // Here is a

问题 How can I do a handles from a control contened in a formview, in code only i can see formview but not the controls in the inserttemplate. thank for any help 回答1: You have to use the FindControl method to find a control. TextBox txtEmail = (TextBox)FormView1.FindControl("ControldID"); This is because the controls that are in the DataBound Controls are not directly accessible. To Access these controls, you have to use the FindControl method and cast it in appropriate control. 来源： https:/

问题 I'm trying to use function SetForegroundWindow(HWND hWnD) . I have some handles but it's not working as parameter of above function. My handle is a thread and I want to run it in foreground. What are the differences between a HWND and a HANDLE? 回答1: They are just abstract data types. According to MSDN, HANDLE and HWND are defined as: HANDLE is a handle to an object. HWND is a handle to a window. So, a HWND is a HANDLE , but not all HANDLE s are HWND . In fact: typedef void *PVOID; typedef

问题 I'm trying to use function SetForegroundWindow(HWND hWnD) . I have some handles but it's not working as parameter of above function. My handle is a thread and I want to run it in foreground. What are the differences between a HWND and a HANDLE? 回答1: They are just abstract data types. According to MSDN, HANDLE and HWND are defined as: HANDLE is a handle to an object. HWND is a handle to a window. So, a HWND is a HANDLE , but not all HANDLE s are HWND . In fact: typedef void *PVOID; typedef

问题 I'm trying to use function SetForegroundWindow(HWND hWnD) . I have some handles but it's not working as parameter of above function. My handle is a thread and I want to run it in foreground. What are the differences between a HWND and a HANDLE? 回答1: They are just abstract data types. According to MSDN, HANDLE and HWND are defined as: HANDLE is a handle to an object. HWND is a handle to a window. So, a HWND is a HANDLE , but not all HANDLE s are HWND . In fact: typedef void *PVOID; typedef

问题 A colleague of mine came across an article on codeproject over the weekend which describes the use of the auto_handle method. Given that the article was written in 2006, is that still the right way to handle deterministic disposal for things like file handles? We've tended to explicitly flush and close file handles and then delete the pointers and null them to be certain the GC has no excuse not to collect them (yes, we know we're super-paranoid). Using something like auto_handle looks like

问题 A colleague of mine came across an article on codeproject over the weekend which describes the use of the auto_handle method. Given that the article was written in 2006, is that still the right way to handle deterministic disposal for things like file handles? We've tended to explicitly flush and close file handles and then delete the pointers and null them to be certain the GC has no excuse not to collect them (yes, we know we're super-paranoid). Using something like auto_handle looks like

问题 how to change the window style of a form outside your app?hard question? i am actually trying to move a form witch is topmost and has no border. i have the handle(hWnd) of the window. i can write thousands of lines of code if guaranteed to work. 回答1: Assuming that this window could be from any app produced from any kind of Win32-based runtime, it looks like you'll have to resort to p/invoke of the core Win32 apis for window operations. For example, you could use SetWindowPos, which can be