64-bit beginner can't get 32- or 64-bit .NET apps to run on 64-bit machine
Hi,
Please forgive this dumb question, but I *just* got my 64-bit (AMD Athlon X2) machine two days ago and am trying to test .NET apps under it. I've gone to Windows Update and installed all available updates. I'm running Windows xp Professional x64 Edition.
The problems I have are this:
I used Visual Studio 2005 Release Candidate on my other, 32-bit machine to build 32-bit and 64-bit binaries of a little app that does nothing but show the size of an IntPtr when the user clicks a button.
I copy the 64-bit app to my 64-bit machine and it crashes on startup. I suspect because I don't have the .NET 2.0 framework on that machine. Where do I get the .NET 2.0 framework for 64-bit?
Second, I copy the 32-bit app to my 64-bit machine and it also crashes on startup. I *should* have the 32-bit .NET framework on that machine as I downloaded all updates from Microsoft Update, right?
Any help would be greatly appreciated. Thanks in advance...
-Eric Harmon
I have installed .Net framwork 1.1 on 64-bit Windows and it works fine. When you are installing it, it will ask you to copy a line and paste it on the Run window, installation will proceed and you will have the 1.1 framework installed.
Keep in mind that most 1.1 assemblies will run perfectly fine under the 32-but 2.0 framework on Windows 64-bit; so there really is no need to install 1.1 unless you *have* to.
With all the Windows-64 bit installations I have done, you just pop in the CD, select to boot from it when prompted and you are good to go.
If you are having problems booting from it, I would suspect the following:
- Error while burning ISO, thus creating a non-functional Windows boot disk
- BIOS is not set to boot from CD as an option
- Your hardware is not 64-bit
Please check these and get back to me.
Also note (and I may be wrong) that apps build with beta 1, beta 2 or the RC will have been built to use the specific version of the .NET Framework that was in those products.
I havent tried it, but trying to execute an app built with RC or a beta on a machine that has only had the final release of VS and .NET installed, will fail.
By default (so far as I understand) .NET enforces versions rigidly, so if the app was built with some (beta) framework classes version 2.0.1.003 (for example) and the final release of the .NET framework is 2.0.1.0105 then it wont load, the app needs the EXACT same version.
Every app (assembly) explicitly specifies the version number for EVERY other assembly that it depends upon, and it is this version and ONLY this version that it will use.
You need to rebuild the app against the current release version of .NET in order to get what you want.
This policy can be changed, but by default it is rigid (I think).
Hugh
