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
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 using VB.net 2010 express, where can I find the compiler option for 64bit? or, it will compile for 32bit only? or, it should work for both 32 and 64 bit in most case?I'm using a 64bit component in the program, vb express reports error when I compile it, but if I use the 32bit compnent, then it is ok.does it mean express 2010 automatically compile to 32bit? or somewhere I should set the win7 64bit (which is what i'm using).just start using win7 64bit & vb express 2010, got confused
I just switched to Win7 Ultimate edition 64bit and now the beep functionality via internal speaker (system speaker on motherboard) does not work anymore.The reason is described here (basically M$ trying to clean up their code):url...I used "Console.Beep(a,b)" to notify me that a process has ended.Any ideas how to send some kind of acoustic signal through the internal speaker (any loud noise would do for my purposes).
I have written a Forms application that analyzes a lot of (~1400) 8-bit jpg images from automated lab-equipment. I am in the process of migrating from WinXP to Win7 and to my surprise I noticed that analysis was 5 times slower under win7 compared to win XP (!?!?!). I investigated further and found that the loading of the jpg images was the step that was takning longer! The simple code demonstrates the problem: On XP i get 70 images per second, but only 12 images per second under win7. Has anyone else noticed this performance drop, and can something be done to improve it?
I know the propertys transparency key and opacity. It isnt what I am looking for. I need to have my form to have the same Glass Effect the as win7 does while runing under win7 plataform. Like, if i have glass effect in the top I should have it in the background.
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?
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'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 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 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 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?
I am using Visual Basic Express 2008 64bit on a Windows 7 64 bit computer. It is running Microsoft Office 2010 University Edition, which only comes in 32 bit so far as I know. I am able to connect to my access .accdb database from within Visual Basic, which I wasn't able to do until I came across this: [Code]...
Beforehand, I had recieved a "Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine." error, and after applying the above fix worked fine. However, now that I am trying to publish my program, I am returned with the same error, no matter what target CPU I select. The program works fine on 32bit machines, however on my 64bit laptop it is unable to connect to the database. I have tried compatibility mode, downloaded many different add-ons from the Microsoft download page, but to no prevail. My understanding is that it is not actually compiling the published version to x86, simply running it as such when I build it in Visual Basic, and because there is no apparent way to set target CPU for compiling,
I developed my application using vs2008 on a 32bit XP machine using ms access. My new machine is Vista 64bit using vs2008. Ms access has stopped working. It is looking for a 64bit software. Is there any? how do I work around this? will this hurt me when deploying to non 64bit machines?
I wonder if/how to use a 32 bit DLL on a 64 bit machine. The situation is like follows:Autocad Inventor(64 bit program) can launch plugin DLL's. The plugin DLL in this case is programmed with VB.NET 2008 Express edition. As far as I know, I can only choose "Any CPU" when building the DLL with the Express edition. This DLL makes uses of a COM object called Isah IERPlink, a piece of software that is used with a 32 bit package. So in my bin directory this DLL will be added "interop.IERPlink.dll". I guess this DLL is specified for 32 bit CPU's, but I'm not sure.