VB 2010 Express Compile Problem

[skisteep]

Hi,
Been using RFreceiver custom compiled from source for many years, my RFX Receive device is circa 2008, using VB 2008. I recently added Win 7 Utimate to my mix and decided to install VB 2010.

First, I took the RFreceiver.exe from my on Win XP Pro built on VB 2008, copied it to my Win 7 computer, ran no problems

Next, I installed the RFreceive project from my Win XP Pro computer into the Win 7 computer with VB2010, installed and compiled without any errors. Started up RFreceive.exe both via VB debug mode and the standalone EXE and I get a buffer timeout error, in other words it isn't reading the RFX device(I think)

So in summary the EXE built on VB 2008 works on Win 7, but the EXE built on VB2010 doesn't, but no compile errors just buffer timeouts.

Note: it isn't the baud settings, the RXreceive console comes up showing 4800, etc in both VB2008 builds as well as VB2010 builds, and I have also checked these settings in Device Manager.

Any hints as to what I'm missing on VB2010 would be greatly appreciated.

Best,
Wayne

[harmen]

64 bits vs 32 bits? Different .Net framework version 2.0 vs 3.x vs 4.x?

[skisteep]

Thanks for the response Harmen,

I had thought about that but couldn't see why the USB device would be handled any differently or have different code.

I checked out RFXCom.com's site for any info on x32 vs x64, and .net stuff, couldn't find anything, do you know where they are going on this??

I'll try to setup VB2010 to build x32 and .Net 3.5(same as on XP Pro)

Best,
Wayne

[xanhoera]

Not sure, but have you checked your firewall settings? Just disable firewall and try running from within VB2010.
I ran into similar problems running socket-related code from within Visual Studio: the firewall doesn't popup to allow/disallow. When running standalone exe it runs fine (after allowing the executable in firewall).

- oops, I somehow missed that it's not connecting to rfxlan, but usb. Ignore pls

[skisteep]

Thanks for your responses, the issue as Harmen pointed out was .Net 4, I changed the compile dependency to .Net 3.5, works okay now.

Best,
Wayne