![]() |
|
|
|
#1
|
|||
|
|||
|
Visual Studio .NET "Whidbey" Technology Preview (PDC) (October 2003)
Microsoft Professional Developer's Conference (PDC) 2003 You can call (prealtha or prototype) or I call (VS2004PDC) Code name: "Whidbey DVD Include : - VS.NET Main Install File Version: 8.0.30703.27 (m2.030828-2105) - NET Framework File Version: 1.2.30703.27 - NET Framework (IA64) File Version: 1.2.30703.27 - NET Framework SDK (x86/IA64) - MSDN : MSDN 2003JAN (support any MSDN xxx2003/xxx2004 (exclude VS6 MSDN)) - Microsoft Visual SourceSafe 2004 File Version: 8.0.30703.27 - Tools and Extras. Visual Studio .NET Community Technology Preview (CTP) (March 2004) You can call (altha) or I call (VS2005CTP) Code name: "Whidbey" (I think formerly "Orcas", So many different between two versions (GUI, Class Wizard and etc.)). DVD Include: - VS.NET Main Install File Version: 8.0.40301.09 (pd4.040301-0900) - NET Framework File Version: 2.0.40301.9 - NET Framework (IA64) File Version: 2.0.40301.9 - NET Framework (AMD64) File Version: 2.0.40301.9 - MSDN: New MSDN 8.0 (very bad edition) + MSDN JAN2003 - Microsoft Visual SourceSafe 2004 File Version: 8.0.40301.9 - Microsoft SQL Server "Yukon" Beta 2 - Tools and Extras. volodya: Quote:
, Yes, it possible to replace JAN2003 to 2004APR (or any 2004xxx) you need to modify msdn.msi, but is to mach work and I don��t have time for this, sorry man Regarding MSDN 8.0, using a new help file format. Rhodium: Quote:
Last edited by Mr.S; 04-19-2004 at 14:47. |
|
#2
|
|||
|
|||
|
Quote:
When will that be released? |
|
#3
|
|||
|
|||
|
Quote:
).Regards, Satyric0n |
|
#4
|
|||
|
|||
|
Mr.S:
According to this page: hxxp://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx "Orcas" is the codename of VS 9.0 (basically the release after VS2005), which will be released in the Longhorn timeframe, with Lornhorn specific development features. VS2005 was always and is still codename "Whidbey". Also, the WinBeta guys say the release that came out on irc.betasirc.net had problems, though they didn't say what specifically. I am uploading the WinBeta release, which they claim is fixed. ![]() Regards Last edited by Satyric0n; 04-19-2004 at 23:41. |
|
#5
|
|||
|
|||
|
Anyone notice how intuitive Visual Basic .net 2003 is? In many instances it tells you what to type before you even type it.
By 2005 it will be child's play. |
|
#6
|
|||
|
|||
|
Once again, thank you for the upload. Re: ��WinBeta�� fix: I may be able to comment only when I download and compare both *.iso files. Re: "Whidbey" or "Orcas": I truly don��t care how it is named, what matters is the quality of the product - Microsoft Developer��s team continues to do an enormous job. Even knowing that this is a beta stage of development, I can only say ��thank you��.
|
|
#7
|
|||
|
|||
|
Maybe this is a stupid question but:
Is VS .net (1 or 2) able to compile "normal" - not .net - exes? Because I think Opcode is always faster - or ...? |
|
#8
|
|||
|
|||
|
My brother's company got the evaluation version and he also installed on his home PC. I must say its pretty impressive. Not only the looks, but the usablity rocks... many cool features. Not much resource hungry either (about the same as the previous version).
|
|
#9
|
|||
|
|||
|
Is this the Visual Studio 2005 Community Technology Preview version?
|
|
#10
|
|||
|
|||
|
how stable is this beta version?
Has anyone tried this new beta version? How stable it is?
I want to get VS .NET and wonder should I get 2003 stable version or try new one. It depends on how stable this beta is... |
![]() |
| Thread Tools | |
| Display Modes | |
|
|