Visual Studio 64 bit
-
So VS installs 64 bit code and uses it as needed, unlike other products that come with a 64 bit installer ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Hmm. I would think, since VS2010 is largely a .NET application, it's JIT'ed to 32-bit or 64-bit either at startup or when it's NGEN'ed at installation time. I believe that's the ugliest sentence I've ever posted online X|. Once more, in English, with feeling: I was under the impression that Visual Studio 2010 is largely a .NET application. That means that it doesn't become 32-bit or 64-bit until it's rendered into native code. That rendering usual happens at startup when the Just-In-Time compiler converts IL byte code to native code. It can also happen at installation time using the Native Image Generator[^] or NGEN tool.
Software Zen:
delete this; -
So, I installed Weven on my Mac, on a new HDD. Then I had a fit, my MSDN just ended, and I only have x86 versions of VS. The whole point here is to try to create a world where VS can build my project more than twice without needing a restart. Turns out there IS no x64 version of VS. What insanity is this ? I assume that means it can't use more than 3 GB of memory ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
If you really have a solution that causes VS to consume more than 1GB of ram after building/debugging for a day, you seriously need to rethink your solution structure and break it into parts. I have my instances of VS running for days, developing solution with >180 projects and VS never needs more than 700Mb of RAM.
-
So, I installed Weven on my Mac, on a new HDD. Then I had a fit, my MSDN just ended, and I only have x86 versions of VS. The whole point here is to try to create a world where VS can build my project more than twice without needing a restart. Turns out there IS no x64 version of VS. What insanity is this ? I assume that means it can't use more than 3 GB of memory ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Ummm.. how else do we think 64 bit software is being made for Windows? And drivers?
-
My problems would go away if VS was not crap. I expected to need an x64 version for it to be able to address enough memory to build my ( not overly complicated ) project.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Christian Graus wrote:
My problems would go away if VS was not crap
Are you sure the problem is with VS?? I think a whole mob disagrees with that sentence, because many people don't have problems even with very complicated projects (including 64bit ones).
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
-
I've no doubt that you've already seen this[^]. It seems that rather like the Curate's Egg it is 64bit in parts.
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.” I wouldn't let CG touch my Abacus! When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is.
-
If you really have a solution that causes VS to consume more than 1GB of ram after building/debugging for a day, you seriously need to rethink your solution structure and break it into parts. I have my instances of VS running for days, developing solution with >180 projects and VS never needs more than 700Mb of RAM.
-
Actually, I wish it would use more RAM sometimes. Drives me nuts when it has to keep banging on the disk all the time while switching between the same couple of windows with a coupla GB unused RAM...
I guess Windows 7 thinks it's smarter to use all those remaining GBs that it displays as free, as disk cache :) Here's hoping that in 5 years storage and working memory will be in one superfast NAND device :)
-
So, I installed Weven on my Mac, on a new HDD. Then I had a fit, my MSDN just ended, and I only have x86 versions of VS. The whole point here is to try to create a world where VS can build my project more than twice without needing a restart. Turns out there IS no x64 version of VS. What insanity is this ? I assume that means it can't use more than 3 GB of memory ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
But VS is possible to compile into x64 environment.You need to set this environment and you cn compile and create executable into x64.You cannot launch new application that you've created, into x32 operating system, because you obtain message that both environment aren't compatible.In this case move your app into x64 OS, also Microsoft and yopu can see your app that become possible to launch.That is not exists is VS 64 bit version, into and for X64 operating system(and i hope compatible with x32 env).This is not very good, also because VS at 64, into OS at 64 shall be all x64 and not like now, where only some operation become available.Achille
-
This, i don't understand. Micro$oft provides 64bit OSes, and development tool is 32 bit. Where they are compiling their own code?
They're using the 32-bit Visual Studio compile and debug 64-bit code.
-
So, I installed Weven on my Mac, on a new HDD. Then I had a fit, my MSDN just ended, and I only have x86 versions of VS. The whole point here is to try to create a world where VS can build my project more than twice without needing a restart. Turns out there IS no x64 version of VS. What insanity is this ? I assume that means it can't use more than 3 GB of memory ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
although VS is a 32 bit application it can produce x86, x86_64, Itanium and even ARM code for windows phone just change the project to 64 bit and you'll get 64 bit apps compiled