I've downloaded the 64bit debug symbols and told the IDE where they were located. But for some reason, VS won't build a 64bit debug EXE.
This is my first time doing 64bit so I never had to worry about it before. Is there something I need to do in the IDE that I don't know about? I went to Project Properties and set things to 64bit debug. But when I compile the program, it makes a 32bit program.
I have an old 32bit vb type app and we're running it on windows 7 64bit sp1. On one computer it works fine, on another it doesn't work right. Do you know how we could debug this and figure out what's causing it? Could a different CPU or bios/chip set have something to do with it?
This is the thing we're using specifically:[URL]...
I'm using Windows 7 and I built a small application that just moves the scrollbar of the current active window to some value.The problem is that nothing happens. I tried using GetScrollInfo too but I only got 0 in the nPos parameter.
This is my declartions and constants:
Private Declare Function GetForegroundWindow Lib "user32" Alias "GetForegroundWindow" () As IntPtr Private Declare Auto Function SetScrollInfo Lib "user32" (ByVal hWnd As IntPtr, ByVal fnBar As ScrollBarDirection, ByRef lpsi As SCROLLINFO, ByVal bRepaint As Boolean) As Integer
[code]....
On the form load I just do a delay of 2000 milliseconds so I could focus on another window, wait and nothing happens.
In the past, perhaps versions of Visual Studio prior to the 2008 that I am using now, I would do something like this in my VB.NET code:System.Diagnostics.Debug.WriteLine("Message")
and the output would go to the output window.Now it doesn't. Something must first apparently be enabled.
If this involves "attaching a debugger", please explain how to do it. It seems to me that it should just work without too much of a fuss.Here's a video explaining the issue in real time and showing you all my settings[URL]..
I opened an older project and it works fine. Using syntax: debug.print ("OK") and look for printed line in immediate window. Is there some setting I could have inadvertently disabled or have maybe discluded some imports? Only import is forms.
Im new to VB 08 and i made a project that runs fine when i debug from inside the VB solution explorer. When i go to my BIN folder and try to run my project, the project runs but the button event seems to be none exsisten, also my message box does not appear on load, it should give an ERROR message if it does not detect the process writen in the module.
the code seems to be working fine when i am debugging but when i run the normal way no sms is send. the following is my code,see where i am going wrong.
dim smsPort As New SerialPort smsPort.PortName = "COM18" smsPort.BaudRate = "921600"
Full Program: Option Strict On : Option Explicit On Module Module1
[Code]...
After I ran it, I had a file a.txt in my debug folder but the size is 0 bytes (and when i open it is empty of course) Shouldn't the output had "asd" in it ?
Simple question that does not seem to be covered: If I use a lot of Debug.WriteLine statements in my code, will they be completely absent in my production version?
I mean: Is the compiler smart enough to not emit any code for those calls? Or would I have to surround them by #if DEBUG..#end if directives?
I'm using the following code to iterate through and find windows containing specific strings in their title bars. I have two projects containing this identical information, yet for some reason - it works when targeted to x64, but FindWindowLike returns 0 always on x86. I need this to run in x86.I am developing this on Windows 7 x64, but it needs to run on my machine as well as XPx32. What I can't fathom is why it compiles/runs on x64 but not x32 (considering I'm targetting user*32*.dll)
i wrote a programm that reads the memory of a program.it worked at xp and vista but not at windows 7 i builded it with microsoft visual basic 2008 express edition.the code looks like this:
Public Declare Function GetWindowThreadProcessId Lib "User32" (ByVal hwnd As Integer, ByRef lpdwProcessId As Integer) As Integer Public Declare Function OpenProcess Lib "kernel32" (ByVal dwDesiredAccess As Integer, ByVal bInheritHandle As Integer, ByVal dwProcessId As Integer) As Integer Public Declare Function ReadProcessMemory Lib "kernel32" Alias "ReadProcessMemory" (ByVal hProcess As Integer, ByVal lpBaseAddress As Integer, ByRef lpBuffer As Integer, ByVal nSize As Integer, ByRef lpNumberOfBytesWritten As Integer) As Integer
coming from VB6 I've been using the windows API for many years. Now I'd lke to do the same on .NetMy question is, what would happen if I build for 'AnyCPU' and the application calls Kernel32 while running on a 64bit machine ?
I have an application that I built in VB.Net 2008 on Windows XP for Any CPU that I would like to run on Windows 7 64bit. Is this possible from Windows XP or do I need to compile and develope on Windows 7 64bit for it to work?
Depending on what component is handling the print for you, some of them are not 64 bit ready (i.e. 32 bit only). To use them you must compile your application as 32 bit only. It will then run on the WOW platform that Win7 supplies.
You change this option on the PropertiesCompile screen. Press Advanced Compile Options and review Target CPU:
I'm getting a new laptop with pretty free hands as to what to get.Most I like come with Windows 7 64bit and I'm a bit cautious about that as I have Vista 64bit on a stationary at home. Not completely happy with that.
I have learned that the Jet database - that I use a lot - does not run on Vista 64bit, but how's the story with Windows 7 64bit. As I will be doing a lot of programming on the new laptop (and I need to get moving again soon - busy!!) I would like to know of potential problems up front.
I had a vb6 applications which using following dll files 1. shell32.dll 2. user32.dll 3. comdlg32.dll 4. apigid32.dll. It is working fine on vista 32bit OS . Now i am trying to run my application on Vista 64bit OS.
Is it working fine on vista 64bit OS with out any changing in vb6 code?Is there any problem with this above mentioned dlls on Vista 64bit OS?
I have used it successfully on 32 bit Win XP VB2008 Express application, but I am having trouble in 64bit Win7 environment.
Specifically the .Connect method is throwing an exception {"The client failed to connect. Make sure the server application is running and that it supports the specified service name and topic name pair."} NDde.DdeException
I have a .net Application that writes text to a serial COM port, a POS reciept printer to be more exact. i am using the Rs232 class library to write and read to a serial device.My problem is now with some clients that have updated their operatingsystem to WIN7 64bit version, have trouble to create a connection to the COM-port. the com-port seemes to get occupied with some other process and that blocks my application to opening a new connection. so for my question, does anyone know how i can close all connections to a com port? or see whats blocking it? once again this seems to only to affect win7 and 64bit users.
Something that is bugging me which My application is targeted for 32 bit machines but I'm not sure which .NET installation package to use with my deployment: 32, 64 or the package with both.I currently bundle the .NET 32 bit installation with my installer and that works fine. I don't have a 64 bit machine to test with, so my question is what version of the framework will my application need on a 64 bit machine?
Long story short, code that used to work on my 32 bit computer doesn't work on my 64 bit computer. Does 64 bit require something like changing Integers -> IntPtrs?