View Full Version : .NET Framework 2.0 released.
Sharktooth
28th October 2005, 18:31
SDK and Redist downloads: http://msdn.microsoft.com/netframework/downloads/updates/default.aspx#.NET%20Framework%202.0%20Beta%20SDK%20and%20Redistributable
Doom9
28th October 2005, 20:12
/me is looking forward to discussing automatic distribution of the new runtime to half the PCs throughout our organization... I simply had everybody install v1.1 manually last time.
But the new features in Visual Studio really make the update extremely worthwhile, and I've been waiting for IPC and encrypted remoting for a while.
int 21h
29th October 2005, 05:45
/me is looking forward to discussing automatic distribution of the new runtime to half the PCs throughout our organization... I simply had everybody install v1.1 manually last time.
But the new features in Visual Studio really make the update extremely worthwhile, and I've been waiting for IPC and encrypted remoting for a while.
SMS?
I actually inadvertently ended up converting the Delphi shop I just came into to .NET using VS2005. I've been using C# Express for a good bit now and really enjoy the overall improvements in the IDE. If only our Microsoft rep could get our MSDN subs straightened out I could grab VS2005 RTM :)
Doom9
29th October 2005, 11:11
I guess I should quickly connect to work and put both VS.NET and SQL server in the download queue so they're there when I get to work on Monday.
I'm not sure our IT has SMS but they definitely have something to distribute software. I guess I just need to send them an .msi of the runtime.
iNFO-DVD
1st November 2005, 13:45
Not that this has anything to do with the thread but;
I installed .NET Framework 2 on my system. I ran avi.NET, which tells you the .NET version at the start of encode, and I noticed it still said v1.1.
I since found out you must uninstall v1.1 hotfix and v1.1 first, reboot, then install v2.0.
Though all .NET programs seem to work fine with .NET v2.0 in, I can't seem to get Visual Studio 2003 to work with it.... so back to v1.1 for me.
Is v2.0 only compatible with the new Visual Studio 2005 ?
Is it my system? Am I doing something silly? Can I get v2.0 working with VS 2003? Maybe I need to install the SDK, hmm, I'll give it a try.
stax76
1st November 2005, 17:26
StaxRip (soon!) is build with VisualStudio 2005 since April, I'm using the new features everywhere. SharpDevelop 2.0 alpha looks very cool as well btw.
Doom9
1st November 2005, 19:02
Unlike other .NET development environments, VS.NET appears to be using its own compiler rather than the sdk compiler (csc) - at least that would explain the sizeable difference in application size. But any IDE using csc should be compatible with 2.0, but certainly won't support command completion for the new syntax. Plus VS.2k5 has some really neat new features.
stax76
1st November 2005, 20:24
I don't see how two different compilers would make sense, at least there should be the same backend. The build process is entirely handled by msbuild and that utilizes the cli compiler, easily test this by temporary renaming csc.exe. :)
btw: every user can build source code without sdk:
"C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\MSBuild.exe" "D:\Projekte\StaxRip\StaxRip.sln" /t:Rebuild /p:Configuration=Release
The solution though must be created (or converted) with VS 2005. SharpDevelop 2.0 will utilize msbuild as well.
Doom9
1st November 2005, 21:00
btw: every user can build source code without sdk:megui even comes with its own build script and logic that allows csc compilation (building in images can be quite the pain because of different resource names as compared to VS.NET compilation)
iNFO-DVD
2nd November 2005, 01:36
C'mon santa, please leave VS 2005 in my stocking next month.
int 21h
2nd November 2005, 06:43
MSBuild is a VS2k5 thing, its supposed to compete with things like Ant.NET, if it really can remains to be seen.
Mutant_Fruit
6th November 2005, 19:04
I installed .NET Framework 2 on my system. I ran avi.NET, which tells you the .NET version at the start of encode, and I noticed it still said v1.1.
I thought the point was that if a program was built using .NET 1.1, it would make calls to .NET 1.1 if it was installed as opposed to 2.0.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.