Actually there’s 2 main reasons that the default project type for WPF applications is x86. Intellitrace debugging only works with x86 and that would look pretty bad if the default project templates didn’t work with one of their star features. Many developers were still not aware of the fact that their AnyCPU exe’s would run … Read more
There is I used this blog post to install it in my machine: http://luminite.wordpress.com/2012/09/06/installing-oracle-database-xe-11g-on-windows-7-64-bit-machine/ The only thing you have to do is replace a registry value during the installation, I’ve done it about three times already, and every time found a different reference on-line, none here on stackoverflow. EDIT: as @kc2001 noted, regedit must be … Read more
I had a similar issue like this before; I couldn’t find any issues in either of our code. BUT what worked for me was changing the compiler. My guess is that GCC is writing deprecated Assembly. If you can decompile your application we could shed more light on the issue but there just isn’t enough … Read more
We’ve been discussing a similar issue on the Chocolatey Google Group. There aren’t any semantics built into NuGet. The requirement wouldn’t be, what processor architecture are you running on. It would have to be what processor architecture is your project targeting. And then that complicates things… you’d have to understand AnyCPU as well. I think … Read more
This is a known problem on x64 systems: This is a known issue on 64-bit OS platform. The reason is that the 64bit OS core does not allow user mode exception through kernal mode stacks. The exception is swallowed by OS sliently. That happens in FormLoad handler, because it is called in an OS callback. … Read more
On 64-bit JVM’s you need the 64-bit SWT. Current versions can be downloaded here: http://archive.eclipse.org/eclipse/downloads/drops/R-3.6.1-201009090800/index.php#SWT Note the first two downloads, the first is for x32, the other for x64. Note: Even on 64bit Windows, if you use the 32bit JVM, you still need the 32bit SWT version!
In case anybody runs across the same thing I did: I had created two new config settings (copied from the Debug config). For some reason “Prefer32Bit” flag was set to true, even though the checkbox was greyed out and unchecked in the project config page. You can fix it by removing the line directly from … Read more
Javascript represents all numbers as 64-bit double precision IEEE 754 floating point numbers (see the ECMAscript spec, section 8.5.) All positive integers up to 2^53 can be encoded precisely. Larger integers get their least significant bits clipped. This leaves the question of how can you even represent a 64-bit integer in Javascript — the native … Read more
Found the problem – The solution is in the way that the two AppPools are configured: Default Website/my_app is using DefaultAppPool where Enable 32-Bit applications is TRUE Beta/my_app -> BetaAppPool is using Enable 32-Bit applications is FALSE Changing BetaAppPool to set Enable 32-Bit applications to TRUE has fixed this problem. Solution was found by @Rick … Read more
I think you should try this: Run cmd.exe as administrator. Type in and run the following two lines of command: netsh winsock reset catalog netsh int ip reset reset.log hit It may say that a reboot is required, but actually that is not necessary. Try to debug your application again, the problem should be solved. … Read more