Downloading :D
What version are you gyys downloading? 32 or 64 bit?
Printable View
Downloading :D
What version are you gyys downloading? 32 or 64 bit?
Just dont go running chkdsk on any secondary drives guys :P
Just started downloading x64 at 8:20 AM. Should be done when I get home from work. I'll download x86 later during my ISP's off-peak period.Quote:
Originally Posted by RobDog888
Dowloading 64 bit Ultimate
Yea Im gonna DL both bits too. Currently only ~30 mins to go for completion of 64bit version
I'm probably going to download 32 bit Ultimate.
Yes, you are correct!Quote:
Originally Posted by chris128
How could we developers, developers, developers ever forget Steve Ballmer, Ballmer, Ballmer? :D
Don't forget that Virtual PC doesn't support 64-bit client OSes so, even if you install on a 64-bit host. As such the x86 version will be required for virtual machines on VPC. I haven't tested out the new virtualisation support in Win7 but I don't think it extends to 64-bit clients.
So best to install 64 bit and run a vm for the 32 bit as we still need to develop with VB6 :D
Hyper V Server supports 64 bit OS's so if you have a spare PC that you can stick that on then jobs a good'un (its free)Quote:
Originally Posted by jmcilhinney
Yes but unfortunately I don't have a spare system that supports virtualisation in hardware, which Hyper V requires. Certain people at home who shall remain nameless won't let me get another system to build a proper server. How humiliating! :(Quote:
Originally Posted by chris128
You are indeed the laughing stock of this community :DQuote:
How humiliating!
Do I have a spare machine that supports virtualization? No :(
I plan on dling x64 Ultimate next November and installing it on my laptop first, then later for dev desktop.
Is there anything w/ VS 2005/2008 and x64 Windows I should know about? I'll be running VS 2005 & VS 2008 on Win7 for both my laptop and my desktop.
The only thing I can think of is that you'll need a hotfix for SQL Server Express 2008 support in VS 2008, unless SP2 has been released by then.Quote:
Originally Posted by JuggaloBrotha
Just tell your cat that it wont get any catnip unless you can buy a new system. :DQuote:
Originally Posted by jmcilhinney
Downloaded both 64 and 32 versions so far. Im thinking of installing the 64bit but then I lose the ability to develop VB6 apps lol. Dont really want to use a vm so I guess I will try 64bit and see how it goes.
Quote:
Originally Posted by jmcilhinney
I have the same problem... I mean I cannot understand why I cannot build a windows 7 box with 4 tb of storage and 8gb of ram to hold music on, I mean my current windows vista ultimate box with 1tb of storage and 4 gb of ram is really starting to show its age and my .mp3's are really struggling to play on it.....
I'll be keeping an XP vm for vb6 and VS 2003 (not that I use VS 2003 much anymore, I actually use vb6 more than VS2003)Quote:
Originally Posted by RobDog888
haha are you implying that you need something like that to run Hyper V Server?? Most modern laptops can run Hyper V :)Quote:
Originally Posted by DeanMc
So far I am totally impressed. It installed fast. Run very slick. And I really like how they took the Mac OS X dock and improved on it.
Woo, just found out that work has a technet subscription...Downloading 7 as I type this :D
Ehm...I've several VS 2003 solutions in production so I have to install VS 2003. Once I fire up the installation, I get the well-known message:
"This machine is missing components required for local Web application and Web service development..."
and Front Page Server Extensions (FPSE) are missing. After some surprise of not being able to install them by turining windows features on and off (they're not included), I came across a few posts which indidate that FPSE are not supported for Win7 and they are no plans to support them on Win7.
Can anyone confirm this? If it's true, it's a problem that I can't work around.
FPSE are not supported in 2008+. For the OS I havent heard yet
Since I've read that VS 2003 doesn't work in Vista it's no surprise that it doesnt work in Win7 either. However, once it's out of beta you can use the XP VM that MS gives you (for Enterprise and Ultimate editions) for free, just run VS 2003 in the VM in Win7Quote:
Originally Posted by ntg
:eek::eek2::eek::eek2:Quote:
Originally Posted by JuggaloBrotha
You're right about VS.2003 and Vista, obviously I've skipped Vista completely.
One of my more Linux-minded colleagues has setup his work PC using Debian. Since we're a .Net shop, he's doing his real work inside a virtual machine, so he's ended up running the OS he should have booted up from virtually and has a (more or less) irrelevant OS as the virtual machine host. The whole scheme just wastes memory, disk space and processing cycles.Quote:
Originally Posted by JuggaloBrotha
The fact that I can't use VS.2003 is a big disappointment to me. I won't seriously consider performing a non-trivial amount of my work under a VM.
Its just the FPSE that are not supported in Vista and 7. If you dont need it then you can still force an install of 2003 just without ASP.NET project support etc.
Unfortunately I need FSPE because I've a few web projects/services in VS.2003 as well. Granted, I could use a VM to host those or run VS.2003 but then I'd be forced to have a VM running all the time or make changes to the solutions and the build scripts to name just a few of the major inconveniences.
I'm a bit frustrated about this. I really like 7 and I was sure there wouldn't be any problems with my upgrade but I can't think a way around this.
Edit: As far as I can gather from this and other web posts, FSPE works on Vista - this is the real reason I was taken by surprise because, if nothing else, Microsoft is a sucker for compatibility. I can't think of a technical reason that would make it impossible to run FSPE under Win7 since they can run under Vista.
Well, you could start using VS 2008 Express editions for the projects since they're free to use and they work on Vista/Win7. The downside is... you'll have to upgrade the projects to VS 2008 and not use VS 2003. Plus side, with VS 2008 you can have them target the 2.0 Framework so the clients don't have to install .Net all the way up to v 3.5. Downside.. the contract, might be a problem.
Indeed it is a problem. I'm not vending here, it is a big problem.
According to StatSVN, I've a few hundred thousand LOCs worth of VS.2003 code which targets a vertical and highly specialized market, and also incorporates customer code (which has been compiled using VS.2003 as well).
The normal rules of routinely upgrading to the latest-and-greatest runtime version of .Net do not apply. For any system-wide change, even one as "trivial" as a recompile, we have to check for forward compatibility issues inhouse, we have to talk the customer into upgrading their own code that we use, allocate resources to do a straight-forward but time consuming system-wide QA test and deploy all the new redistributable packages.
These days, it's increasingly difficult for me to sell to the customers features that save production time from their people...to say nothing about persuading them to perform an upgrade to the .Net 2.0 runtime. The business value just isn't there.