MS Developers

[greggpb]

I have been using vista64 and win7 64 at home and like the speed and the ability to address 8gb of RAM.. is anyone using vs.net on a 64bit OS ?

I have tried it at home and it doesn't really allow for all the debuggin feature's ?
like changing the code or variables at run/debug time


Are developers stuck on 32-bit ? looks like VS.net 2010 is 32bit only as well

 

[MielieSpoor]

does it really matter? The only thing that really matters is that the compiler can spit out a 64bit assembly/executable - which it does, so I don't really see the problem?

 

[guest2013-1]

beh, I won't go 64 bit for still quite some time

 

[greggpb]

mean that things like changing code or variable values at debug time is not possible...

These features make it easier when you are tracing and want to quickly change something..

 

[guest2013-1]

mean that things like changing code or variable values at debug time is not possible...

These features make it easier when you are tracing and want to quickly change something..

I'm used to it by now with vs.net 2005 when they took out that feature. So I don't really mind. I also define all my variables the 64bit way anyway, no Int32 for me thanks...

 

[dequadin]

I'm used to it by now with vs.net 2005 when they took out that feature. So I don't really mind. I also define all my variables the 64bit way anyway, no Int32 for me thanks...

Why would you do this?

C# assumes int for the result of all arithmetic calculations, unless for specify.. Sure you can implicitly convert from int to long, but aren't you avoiding the type safety a bit by declaring everything long?

Sounds dodgy to me...