vista64

Drag and drop from Windows File Explorer onto a Windows Form is not working

|▌冷眼眸甩不掉的悲伤 提交于 2019-12-20 21:34:08
问题 I'm having an issue dragging a file from Windows Explorer on to a Windows Forms application. It works fine when I drag text, but for some reason it is not recognizing the file. Here is my test code: namespace WindowsFormsApplication1 { public partial class Form1 : Form { public Form1() { InitializeComponent(); } private void Form1_DragDrop(object sender, DragEventArgs e) { } private void Form1_DragEnter(object sender, DragEventArgs e) { if (e.Data.GetDataPresent(DataFormats.Text)) { e.Effect

Drag and drop from Windows File Explorer onto a Windows Form is not working

百般思念 提交于 2019-12-20 21:30:30
问题 I'm having an issue dragging a file from Windows Explorer on to a Windows Forms application. It works fine when I drag text, but for some reason it is not recognizing the file. Here is my test code: namespace WindowsFormsApplication1 { public partial class Form1 : Form { public Form1() { InitializeComponent(); } private void Form1_DragDrop(object sender, DragEventArgs e) { } private void Form1_DragEnter(object sender, DragEventArgs e) { if (e.Data.GetDataPresent(DataFormats.Text)) { e.Effect

How can 32-bit application find the location of 64-bit Program Files directory on Windows Vista 64-bit?

依然范特西╮ 提交于 2019-12-19 05:56:29
问题 I'm struggling with a problem of how to determine the location of the 64-bit Program Files directory on 64-bit Windows Vista from a 32-bit application. Calls to SHGetKnownFolderPath(FOLDERID_ProgramFilesX64) do not return anything. The MSDN article KNOWNFOLDERID also states that this particular call with FOLDERID_ProgramFilesX64 is not supported for a 32-bit application. I would like to avoid as much as possible hardcoding the path to "C:\Program Files". Doing something like

DirectX SDK (June 2010) Installation Problems: Error Code S1023

≯℡__Kan透↙ 提交于 2019-12-17 22:59:58
问题 I seem to be having some problems installing the DirectX SDK. Everything seems to be going well during the install, but at the end I get the message: Setup failed. Errors were encountered during installation of redistributable packages. Please close all open programs and try running setup again. If problems persist, contact DirectX Developer Support. Error Code: S1023 Well, I have tried closing all open programs and installing again but I get the same error. What is error code S1023 ? I tried

How can I call ActivateKeyboardLayout from 64bit Windows Vista using VBA

江枫思渺然 提交于 2019-12-12 10:49:15
问题 Running VBA under XP I was able to call ActivateKeyboardLayout to switch my input language from English to another language. However, this no longer works under Vista64. Any suggestions or workarounds? The code that used to work under XP was similar to the following: Private Declare Function ActivateKeyboardLayout Lib "user32" ( _ ByVal HKL As Long, ByVal flags As Integer) As Integer Const aklPUNJABI As Long = &H4460446 ActivateKeyboardLayout aklPUNJABI, 0 There was a suggestion to try Public

Incorrect QFileInfo permissions for user desktop on vista 64

我的未来我决定 提交于 2019-12-11 16:05:30
问题 I am using the following code to determine if I can write to a specific directory using QFileInfo: QFileInfo dinfo(dirname); if (dinfo.exists()) valid = dinfo.isWritable() Unfortunately, when I pass in the path of the current user's desktop on Vista 64: C:\Users\USERNAME\Desktop QFileInfo::isWritable() returns false. However, if I pass it another directory (say C:\Temp) it returns true. I requested the directory permissions from the QFileInfo object which were 5555 (not writable by anyone).

Vista 64-bit Development Caveats

一曲冷凌霜 提交于 2019-12-06 06:11:37
问题 I'm migrating my development workstation from 32-bit Vista to 64-bit Vista. The production platform is 32-bit Windows Server and SQL Server 2008. Does anyone know of any issues with migrating the code base? EDIT: the system consists of web forms, c# code, stored procedures. there is also ajax.net, ssrs, ssis, and dynamic reports/graphs from dundas. however, i think other users might appreciate any lessons learned or feedback in general regarding this move. FINDINGS: As of Jan 24, 2009

WSE client project keeps reverting WebServicesClientProtocol to SoapHttpClientProtocol

可紊 提交于 2019-12-06 04:10:42
问题 Despite enabling WSE 3.0 on client projects in Visual Studio 2005, web references I make always end up with service proxies derived from SoapHttpClientProtocol. I have to manually change the inheritance to WebServicesClientProtocol, but updating it will revert back to SoapHttpClientProtocol. I am unsure where in Visual Studio project properties can I get it to permanently use WebServicesClientProtocol? As far as I have read, Visual Studio is supposed to generate the regular

Vista 64-bit Development Caveats

自古美人都是妖i 提交于 2019-12-04 11:01:07
I'm migrating my development workstation from 32-bit Vista to 64-bit Vista. The production platform is 32-bit Windows Server and SQL Server 2008. Does anyone know of any issues with migrating the code base? EDIT: the system consists of web forms, c# code, stored procedures. there is also ajax.net, ssrs, ssis, and dynamic reports/graphs from dundas. however, i think other users might appreciate any lessons learned or feedback in general regarding this move. FINDINGS: As of Jan 24, 2009 Checkpoint VPN does not support Vista 64 (actually it seems that very few do) Cropper utility required special

Drag and drop from Windows File Explorer onto a Windows Form is not working

余生长醉 提交于 2019-12-03 06:59:35
I'm having an issue dragging a file from Windows Explorer on to a Windows Forms application. It works fine when I drag text, but for some reason it is not recognizing the file. Here is my test code: namespace WindowsFormsApplication1 { public partial class Form1 : Form { public Form1() { InitializeComponent(); } private void Form1_DragDrop(object sender, DragEventArgs e) { } private void Form1_DragEnter(object sender, DragEventArgs e) { if (e.Data.GetDataPresent(DataFormats.Text)) { e.Effect = DragDropEffects.Copy; } else if (e.Data.GetDataPresent(DataFormats.FileDrop)) { e.Effect =