Vista compatibility

I've been searching for information regarding whether applications based on older versions of VFP (say 6.0) will encounter problems running on Vista. The solution itself is 100% VFP running against a VFP database. Has anyone seen any issues

Thanks in advance!

Visual FoxPro1

Dan Lingman wrote:
Looking for any hints on when a Vista version will be released.

You're not going to find any.

Dan Lingman wrote:
(Note that I'm in the middle of installing the same version as everyone else is right now, but the web site says it won't be out for a bit).

I really don't want to put a third OS on my system just so I can run xna express. (I've already got Vista Ultimate 32 and 64 bit on here - starting to get crowded)

Some people have had luck getting GSE to run under Vista. Have you tried installing it

As far as I know, only the VFP 9.0 extensions (code name Sedna) will actually be tested for Vista compatibility. Whether earlier versions will run is an issue I am not qualified to comment on.

There is some information on the VFP Home Page at: http://msdn.microsoft.com/vfoxpro/letters/

Yup. It made it to a certain point, then failed, and rolled back. Nice to see something do the right thing if it can't install fully.

I'll probably purge off vista 32 bit, and put an xp pro partition back on. That leaves me 64 bit vista for spiffy stuff, and 32 bit xp pro for game development.

Sigh. Another os install.

Dan.

The compatibility issues are due to VS compatibility so if you get VS SP1 and the VS Vista patch (in beta) then a lot of us are sucessfully running on Vista.

The only problem I am seeing is the the VS Version selector app (which is what is run when you open a .sln file) doesn't work at all and I am having to open VS and then use file/open to open my solution.

Yep I see the same thing, the correct icon shows up in Explorer for the project but if you try to double click on it, it doesn't launch C# Express. If you run C# Express then open the solution it's fine. I did spend a day or so getting the service pack and patch in place when migrating to Vista.

I got it working on Vista in a matter of minutes following these instructions...

http://www.nuclex.org/articles/xna-game-studio-express-1-0-on-vista

Other than the issue entioned above, it's working fine. haven't tried running a game on the 360 yet, but I doubt there will be any issues.

Agreed, I installed it on Vista just the other day. As long as you install everything from an elevated rights command line, and in the right order, you should be ok.

Sounds good. Will try this set of instructions when I get home. Maybe I forgot to ask, but are you doing this under Vista 32 bit or 64 bit (I'm running 64 bit)

At worst, I'll work in virtual PC. Slightly better than paving my machine and installing xp from scratch, then vista to a different drive.

Cheers, and thanks for posting that link.

Dan

Are you sure a virtual machine will give you the the graphics hardware support you will need

I'm running XNA on 32bit vista, pretty much following the same instructions that others have posted on this thread. Not to sure how it will run on 64 bit.

Ely is correct - you won't be able to run XNA apps on the PC under virtual PC. XNA requires a SM2.0 card and VPC doesn't emulate any accelerated hardware. You used to be able to run DirectX apps using the ref rast but I don't think that is availale under XNA.

Of course you can always deply to the 360 and test there from VPC.

Has anyone gotten XNA in Vista to deploy to the Xbox 360 and run

Yes working just fine for me.

Well, major thanks to the people on this forum. I've now got game studio running under Vista Ultimate 64 bit. Time to get to work on my game, although I'll really be spending the next week or two doing design, and just futzing with xna to test some ideas out for now.

Cheers, and thanks again.

Dan Lingman

NoGotoGames.com

Cool, good to hear it works on x64 as well.

One issue I have had on Vista is that you need to run the XACT tool as administrator or it will crash as soon as you start it. This is a known issue (even in the December 2006 DirectX SDK) but it works fine as administrator.