Exetools

Exetools (https://forum.exetools.com/index.php)
-   General Discussion (https://forum.exetools.com/forumdisplay.php?f=2)
-   -   Visual Studio 2005 preview is out (https://forum.exetools.com/showthread.php?t=3955)

Rhodium 04-18-2004 04:38

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?

Satyric0n 04-18-2004 06:07

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. :cool:

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

nine 04-18-2004 11:06

Which is the version of VC++ in it? 7.2 or even 8?

Satyric0n 04-18-2004 12:14

Quote:

Originally Posted by nine
Which is the version of VC++ in it? 7.2 or even 8?

VS 2005 is version 8.0.

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

Mr.S 04-19-2004 05:04

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:

I'd upload it to the FTP��
Can you check your upload speed from your site?
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

volodya 04-19-2004 05:33

Mr.S

Sorry, man, I'm probably stupid, but I cannot find it on ftp... :(

Satyric0n 04-19-2004 05:47

Quote:

Originally Posted by Mr.S
Satyric0n:

Can you check your upload speed from your site?
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.

My upload speed is 30-33k/sec. I would be happy to upload this, but in the interest of not wasting FTP space, I will wait until Aaron deletes your unfinished upload before I start. So, to make it official...

Aaron, would you mind deleting the /incoming/Microsoft.Visual.Studio.2005.CTP folder on the FTP so I can reupload from scratch?

Regards,
Satyric0n

Mr.S 04-19-2004 06:08

I will stop uploading for now,
You can start upload now and if you get good speed just continue, and then create Dir in /incoming/Microsoft.Visual.Studio.2005.CTP/ like �� Admin, Please Delete All��.

Thank you for upload, many members will very happy.

volodya:
Quote:

... but I cannot find it on ftp
use "list" ftp account.

volodya 04-19-2004 10:58

use "list" ftp account

����ڧߧ��� �� �ڧ���ݧߧ֧ߧڧ� :)

Guys, I'm also curious about one thing. What about MSDN to 2005? Will usual 2003/2004 MSDN work or it is not backwards compatiable (usual M$ habbit...)

Rhodium 04-19-2004 11:24

Remember that this is a long way from a final release, ...but I think it's fairly stable.

I don't think there is a VS 2004 as such, is there?

I think it's just VS 2003 + 2004 MSDN, and updates.

Mr.S 04-19-2004 13:18

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:

...What about MSDN to 2005......is not backwards compatiable
Plus 1GB for MSDN 8.0 on your HDD :),
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:

...I don't think there is a VS 2004 as such...
hxxp://www.msdnaa.net/content/?ID=2210

Rhodium 04-19-2004 15:41

Quote:

Originally Posted by Mr.S

hxxp://www.msdnaa.net/content/?ID=2210

So there is a VS 2004.

When will that be released?

Satyric0n 04-19-2004 17:57

Quote:

Originally Posted by Rhodium
So there is a VS 2004.

When will that be released?

Err.. It won't be released, at least not under that name. VS2004 was simply renamed to VS2005 (which is still pre-beta, and so may yet be renamed to VS2006 before RTM ;)).

Regards,
Satyric0n

Satyric0n 04-19-2004 23:25

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

Rhodium 04-20-2004 02:13

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.

Mr.S 04-20-2004 10:50

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��.

kksh_1942 04-20-2004 17:01

Vs.Net 2005
 
It is very Buggy and it is not optimised so you can not use it as adevelopmet tool

Hades32 04-21-2004 20:56

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 ...?

qwerty3 04-21-2004 21:48

Quote:

Originally Posted by Hades32
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 ...?

Only Visual C++. Other products compile only to ".net precode".

fsheron 04-21-2004 23:18

Is VS2005 support refactory the C++ source code?

saurabh 04-22-2004 19:53

impressive
 
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).

stevematulis 04-23-2004 14:39

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

shadower 04-23-2004 14:48

Is this the Visual Studio 2005 Community Technology Preview version?

kesipyc 04-23-2004 23:43

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...

Satyric0n 04-24-2004 06:46

shadower, yes this is the March '04 CTP.

kesipyc, I have been using it a lot for the past week or so. There are some obvious bugs, but most are very small. All the major bugs (there are only a few that potentially impact me) that I have seen were listed in the Known Issues section of the release notes on the DVD.

The new features are awesome, but I would not necessarily recommend using this. VS2005 only compiles apps for the .Net Framework 2.0 (except for VC++ which can still compile for native x86, obviously); the binaries are not backwards compatible with .Net 1.x.

So if you plan to run any programs you compile in a VS .Net language (C#, VB.Net, J#, MC++, etc) on a computer with only .Net Framework 1.x (2.0 is not publicly available), then VS2003 will be a much better choice.

Regards,
Satyric0n

siddhartha 04-25-2004 09:45

So if it is that stable when the final version will be released? And is it going to be compatible with MSDN 2004? I just want to be sure if it is worth downloading this preview...


/siddhartha

Satyric0n 04-25-2004 10:28

I believe the final version of VS2005 is slated to be released in March 2005.

Also, I think your MSDN question has already been answered, as you would see if you would simply read the whole thread...

Regards,
Satyric0n

butter 04-29-2004 04:19

Quote:

Originally Posted by fsheron
Is VS2005 support refactory the C++ source code?

As the preview copy currently stand, you can only refactor c# code.

Mr.S 05-09-2004 00:22

Quote:

��
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 ��
After I compared both releases from ��betasirc�� and ��winbeta�� - they are identical.

Satyric0n 05-09-2004 02:48

Quote:

Originally Posted by Mr.S
After I compared both releases from ��betasirc�� and ��winbeta�� - they are identical.

Typical release group competition then, I guess... :rolleyes:


All times are GMT +8. The time now is 18:44.

Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2026, vBulletin Solutions, Inc.
Always Your Best Friend: Aaron, JMI, ahmadmansoor, ZeNiX