Deployed Program Fails on Win64. w 32 bit Processor

[Gruff]

I am running VS.NET 2008 Standard Edition comiling a Visual Basic application with the compile option set for "Any CPU".

 

My deployed application runs as it should on Win32 w 32 bit Processor but fails on a Win64 OS w 32 bit Processor.

 

Is the a limitation of VS.NET 2008 standard? I was under the impression it was the 64 bit processor it wouldn't support.

 

One other tidbit. On the Win64 PC there is a "Program Files" folder for 64 bit applications and a "Program Files (x86)" folder for 32 bit programs.

 

It correctly installs to the "Program Files (x86)" folder. Could the path be the issue?

 

[Edit] Weird. Created a Hello world program and physically copied the executible to the Win64 PC. It works fine. ???[/Edit]

 

[Edit] I'm downloading and installing VB.NET 2008 Express as we speak. *heh* Perhaps if I recomile the program under Win64 it will work. I may also download and install MS SQL Server Express. This is a datacentric app. It ties into an old ProvideX DB through OLEDB.[/Edit]

 

[Edit]( Next Day) Okay. Loaded VB.NET on the Win64 PC. Copied the solution. Loaded and Ran. Error city. Thread errors on a timer event in my splash screen. Very odd. Turned of a couple of compile options. Now it gets past that and says it cannot find the proper DB driver. Ack. This PC runs VB6 compiled programs that connect to the same database so that seems odd too.

 

Maybe I'll just have to bite the bullet and downgrade to Standard WinXP.

 

Can anyone confirm that VB.NET 2008 Standard edition will not work with WinXP 64?

 

[/Edit]

 

 

~T

Edited July 25, 2008 by Gruff

[PlausiblyDamp]

What kind of errors are you getting when attempting to run the application on a 64bit OS compared to on a 32bit OS?

 

When you say it 'errors on a timer event' what is the error you are getting? What is the timer event trying to do?

[Gruff]

I reformatted the hard drive and installed standard WinXP. I no longer have issues with that PC. Of course I suppose I will when we upgrade to Vista64 at some time in the future. I'll need to tighten my belt and opt for the more expensive version of VS at that time I suppose.

 

The error was about calling a variable from one thread when in another. It errored on a line that simply set a label caption to a variable declared inside the timer event. Seemed odd that it would give that sort of error. The timer control was on a splash screen that was a separate thread as well seeing as how I used the VB.NET functionallity to launch a splash screen while reading some intitial data from my DB.

 

I received other errors as well. Unfortunately I do not remember exactly what they were complaining about.

 

In any case thank you for the reply

[PlausiblyDamp]

Updating the UI from a non-UI thread is a no no anyway, perhaps win64 is less tolerant than win32 on these matters.