Visual Studio 2005 preview is out

[Mr.S]

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

It is very Buggy and it is not optimised so you can not use it as adevelopmet tool

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

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

Is VS2005 support refactory the C++ source code?

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

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

Is this the Visual Studio 2005 Community Technology Preview 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...

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

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

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

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]

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

Originally Posted by Mr.S

After I compared both releases from ��betasirc�� and ��winbeta�� - they are identical.

Typical release group competition then, I guess...