|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
WinXPx64 questionHi,
I have a question regarding the .NET Framework 2.0 and x64. I realise these are still in beta, but I hope someone can help me. If i had dotnet2.0x64 installed on winxpx64. Does an application compiled on a winxpx86 (using dotnet2.0x86) require the x86 or x64 edition of dotnet2.0? I'll try to rephrase that a little better just in case you didn't get it. Does a 32bit .net application require the 32bit .net framework edition, or can it use the 64bit .net framework edition? Thanks guys, Tim. would be interesting to know... more like going from 16 to 32 bit in middle
to late 90s... i am sure there is some compatablity involved... like it was for 16 to 32... , so I am hoping 32-bit can still runt with 64bit edition... VJ Show quote "Timothy V" <tri***@msn.com> wrote in message news:uKL372ALFHA.1156@TK2MSFTNGP09.phx.gbl... > Hi, > I have a question regarding the .NET Framework 2.0 and x64. I realise > these are still in beta, but I hope someone can help me. > > If i had dotnet2.0x64 installed on winxpx64. Does an application compiled > on a winxpx86 (using dotnet2.0x86) require the x86 or x64 edition of > dotnet2.0? > > I'll try to rephrase that a little better just in case you didn't get it. > Does a 32bit .net application require the 32bit .net framework edition, or > can it use the 64bit .net framework edition? > > Thanks guys, > > Tim. > Well, since managed code (IL) is JIT compiled, why would your code be specific
to any platform? Wasn't this the whole point? Now, of course, if you make unmanaged calls that assume a platform (x86 or otherwise) then you're stuck with that platform. And thus the new /platform compiler switch. By default the value is "anycpu" which means you don't make any platform specific assumptions in your code. -Brock DevelopMentor http://staff.develop.com/ballen Show quote > Hi, > I have a question regarding the .NET Framework 2.0 and x64. I realise > these > are still in beta, but I hope someone can help me. > If i had dotnet2.0x64 installed on winxpx64. Does an application > compiled on a winxpx86 (using dotnet2.0x86) require the x86 or x64 > edition of dotnet2.0? > > I'll try to rephrase that a little better just in case you didn't get > it. Does a 32bit .net application require the 32bit .net framework > edition, or can it use the 64bit .net framework edition? > > Thanks guys, > > Tim. > Well, the way i see it is that if an x86 compiled .net application (only
managed calls) were to be able to use the x64 edition of the .net framework, wouldn't the application then be running in both x86 and x64 mode? The application being x86 and the managed calls being x64, there could possibly be a performance increase for the x86 application since the calls to .net are now x64. I don't have winxpx64 cpp installed, so i'm unable to test the question i have asked. So i thought someone in the newsgroups may have asked themseleves this question and had tested it. Show quote "Brock Allen" <bal***@develop.com.i_hate_spam_too> wrote in message news:39319632467664522003120@msnews.microsoft.com... > Well, since managed code (IL) is JIT compiled, why would your code be > specific to any platform? Wasn't this the whole point? > > Now, of course, if you make unmanaged calls that assume a platform (x86 or > otherwise) then you're stuck with that platform. And thus the new > /platform compiler switch. By default the value is "anycpu" which means > you don't make any platform specific assumptions in your code. > > -Brock > DevelopMentor > http://staff.develop.com/ballen > > > >> Hi, >> I have a question regarding the .NET Framework 2.0 and x64. I realise >> these >> are still in beta, but I hope someone can help me. >> If i had dotnet2.0x64 installed on winxpx64. Does an application >> compiled on a winxpx86 (using dotnet2.0x86) require the x86 or x64 >> edition of dotnet2.0? >> >> I'll try to rephrase that a little better just in case you didn't get >> it. Does a 32bit .net application require the 32bit .net framework >> edition, or can it use the 64bit .net framework edition? >> >> Thanks guys, >> >> Tim. >> > > > > Well, the way i see it is that if an x86 compiled .net application Well, that mode is called "anycpu" :) But don't think of it being x86 compiled... > (only managed calls) were to be able to use the x64 edition of the > .net framework, wouldn't the application then be running in both x86 > and x64 mode? It's compiled to IL. IL is platform independant and when it hits a IA64 CLR, then it'll be IA64 JIT compiled. So, I think we're on the same page here. -Brock DevelopMentor http://staff.develop.com/ballen I think you'll be able to say when you install it (or build it). You could
easily do things that would be specific to a 32-bit processor (int instead of IntPtr in p/invoke) so you'd need to make sure you've written agnostic code. So there'll be something like AnyCpu, and something else to say 32 or 64-bit specific. -- Show quotePhil Wilson [MVP Windows Installer] ---- "Timothy V" <tri***@msn.com> wrote in message news:uKL372ALFHA.1156@TK2MSFTNGP09.phx.gbl... > Hi, > I have a question regarding the .NET Framework 2.0 and x64. I realise these > are still in beta, but I hope someone can help me. > > If i had dotnet2.0x64 installed on winxpx64. Does an application compiled on > a winxpx86 (using dotnet2.0x86) require the x86 or x64 edition of dotnet2.0? > > I'll try to rephrase that a little better just in case you didn't get it. > Does a 32bit .net application require the 32bit .net framework edition, or > can it use the 64bit .net framework edition? > > Thanks guys, > > Tim. > > "Timothy V" <tri***@msn.com> a écrit dans le message de news: uKL372ALFHA.1***@TK2MSFTNGP09.phx.gbl...> Hi, VS 2005 has a new setting that lets you specify whether your assembly will > I have a question regarding the .NET Framework 2.0 and x64. I realise > these are still in beta, but I hope someone can help me. > > If i had dotnet2.0x64 installed on winxpx64. Does an application compiled > on a winxpx86 (using dotnet2.0x86) require the x86 or x64 edition of > dotnet2.0? > > I'll try to rephrase that a little better just in case you didn't get it. > Does a 32bit .net application require the 32bit .net framework edition, or > can it use the 64bit .net framework edition? target x86, x64 or both cpus. The default mode is to target both cpus. With this setting, the same assembly can run either on x86 or x64, and the JIT takes care of the differences. Marking the assembly as x86 or x64 is useful if your assembly relies on unmanaged DLLs that don't exist in both flavors. Bruno. Show quote > > Thanks guys, > > Tim. > > question regarding the .NET Framework 2.0 and x64
http://msdn.microsoft.com/chats/transcripts/windows/windows_110904b.aspx
--
Thomas Scheidegger - MVP .NET - 'NETMaster' http://www.cetus-links.org/oo_dotnet.html - http://dnetmaster.net/ 
|
|||||||||||||||||||||||
Other interesting topics