![]() |
|
|
|
#1
|
|||
|
|||
|
Visual Studio 2005 preview is out
It's been released to testers.
http://msdn.microsoft.com/vs2005/preview/default.aspx Does anyone have any screenshots? Last edited by Rhodium; 08-31-2004 at 04:26. |
|
#2
|
|||
|
|||
|
I downloaded the DVD ISO a few days ago, but haven't installed it yet. Once I do, maybe I'll post on how it is. From all accounts I've heard, it's pretty sweet.
![]() I'd upload it to the FTP, but I see that Mr.S already is in the process of doing so; or, he was until the FTP ran out of disk space, anyway.. If anyone wants to download this ISO, Winbeta is hosting it; get it from one of the LH-* servers, as they are by far the fastest. Regards, Satyric0n |
|
#3
|
|||
|
|||
|
Which is the version of VC++ in it? 7.2 or even 8?
|
|
#4
|
|||
|
|||
|
Quote:
As far as I know Visual Studio versions are getting incremented in sync with the .Net Framework now. VS2002 was 7.0, matching .Net 1.0; VS2003 was 7.1, matching .Net 1.1; VS2005 is 8.0, matching .Net 2.0. Regards |
|
#5
|
|||
|
|||
|
Yes, VS 2005 was out a month ago on irc.betasirc.net
(devenv.exe - v8.0.40301.9) with NET Framework v2.0.40301.9 Old versions of NET Framework will not work with this release v1.2.30703 �C from VS 2004 v2.0.31113 - leaked v2.0.40226 - leaked VS2002(7.0) = 1.0 VS2003(7.1) = 1.1 VS2004(8.0) = 1.2 VS2005(8.0) = 2.0 If you have VS 2004 on you machine, you would need to uninstall VS 2004 this version and v1.2.30703 Framework: Reason being: v1.2.30703 and v2.0.40301 are using same registry setting and VS 2004 does not support v2.0.40301 Regarding MSDN on 2005: Microsoft pushed out a new MSDN scheme which looks like it is not supported by old VS 2003. Satyric0n: Quote:
For some strange reason for the past month I can��t get a good upload speed. If your can get more than 15kBps it will be much faster. Then I can delete mine to make more space on ftp drive. Meanwhile I will resume my upload but it��ll take some time. Fastest way to get VS2005 is from IRC. PS: Just a suggestion, before installation make backup: C:\WINDOWS\system32\config C:\Program Files\Common Files\Microsoft Shared C:\WINDOWS\system32 |
|
#6
|
|||
|
|||
|
Mr.S
Sorry, man, I'm probably stupid, but I cannot find it on ftp...
|
|
#7
|
|||
|
|||
|
Quote:
Aaron, would you mind deleting the /incoming/Microsoft.Visual.Studio.2005.CTP folder on the FTP so I can reupload from scratch? Regards, Satyric0n |
|
#8
|
|||
|
|||
|
Vs.Net 2005
It is very Buggy and it is not optimised so you can not use it as adevelopmet tool
Last edited by kksh_1942; 04-20-2004 at 17:11. |
|
#9
|
|||
|
|||
|
VS.NET 2003 and above are (in my opinion) only really useful if
- you've made the jump to .NET (C#, VB.NET, or ASP.NET) - you have no more dependency on old VC++6 CRuntime I develop extension DLLs for an app developed with VC++6 and made the mistake of trying to move my VC++6 projects to VS.NET 2003. I learned the hard way that the C-runtimes are incompatible if you are allocating memory in your DLL (built with VS.NET) and giving it back to the app (built with VC++6) that loads your DLL, since you're simultaneously using two versions of the C-runtime. Crash and burn time! Also... learned the hard way that once you upgrade a development machine from VC6 to VS.NET, you really can't go back - your machine will be hosed if you attempt to revert. Anyhoo... I like the new interface and am waiting for the day that I can kick VC6 to the curb and get the better-threaded STL, nicer UI, etc. SM |
![]() |
|
|