>> When .Net 4.0 comes out (which will be the third version of the framework) then you will have to worry about porting your apps.Erm, .net is designed to be forward compatible, yes forward meaning .net 1.0/2.0/3.0 apps should always work on the latest version of the runtime. I'm sure there have been *some* compatibility problems in the past, but generally you don't need to worry about it.
I'll tell you, this division of Microsoft has really caught on to the open-source agile movement. I'm an ASP.NET developer (I'm attending this years ASP.NET conference and am writing from hotel room of Mandalay Bay in Sin City, actually), and am so impressed with the Microsoft guys responsible for this technology -- Scott Guthrie, General Manager with the Microsoft Developer Division especially. This guy works hard for the betterment of the community - check out his blog on .NET technologies (ASP.NET especially). <a class="user" href="http://weblogs.asp.net/scottgu/">http://weblogs.asp.net/scottgu/</a> The ATLAS, now MS AJAX framework development goes to show how Microsoft is integrating with the developer community to get things out the door quickly in a way never seen before.And yes, the VS 2005 development environment is unrivaled...
@theonesteve "While .NET apps may cause the issues you've mentioned, can you really say Java apps don't?'One big issue I have with java is that if you want to distribute your app and don't have time/resources to WASTE on support - then you had better ship it with it's own JVM. Which is not a problem per se, ('cept the huge download size - particularly on Linux).The problem comes when the user runs more than one java app, these apps then each run in their own VM, resulting in massive bloat.
And your point is what exactly? Just because they haven't released one for 2.0 doesn't reflect anything on the 3.0 code.If your point was somehow that each version was getting progressively better then I'd have to point you to their history of OS development and the number of and number fixes in each service pack that have been released for each version released has ballooned. But I guess that has no reflection on MS's general level of released quality code to you.So what was your point exactly?
*sigh*Any language you write in .NET goes down to MSIL (Intermediate Language - the Assembly language of the managed .NET environment) which then gets JIT'd (Just In Time compiled) when you run the EXE.But but but but siir... isnt that what Java does already? Yes son, it does do that but Java uses Byte code, which isnt quite as readable as IL is. The Java platform has only one language, Java, whereas .NET can support any number of languages that stick ot hte rules defined by the CLI.So essentially, if you write a .NET Application, it will get JIT'd cached, or alternatively you can use the NGen tool to avoid that process and have an almighty orgy of JIT'ing for all your signed .NET assemblies.
Is that why ASP.NET is now used daily by more than 2 million professional developers worldwide, and that it runs some of the most successful websites and applications in the world, including the most heavily visited site on the web today: MySpace.com (which now handles more than 1.5 billion page views each day using ASP.NET 2.0). Not that I'm a big MySpace fanboy, but "fair is fair", pal.
Get a clue. What .NET .EXEs are you talking about? The MSIL gets JIT compiled to native code. Run the same app a couple of times and you will notice that it gets faster and faster - because it gradually gets compiled to native code.A totally different issue is if some idiot drag & dropped some crap together and his app has 50000 wizard-generated lines of code.
mikewellerNov 8, 2006
>> When .Net 4.0 comes out (which will be the third version of the framework) then you will have to worry about porting your apps.Erm, .net is designed to be forward compatible, yes forward meaning .net 1.0/2.0/3.0 apps should always work on the latest version of the runtime. I'm sure there have been *some* compatibility problems in the past, but generally you don't need to worry about it.
kelwayNov 8, 2006
I'll tell you, this division of Microsoft has really caught on to the open-source agile movement. I'm an ASP.NET developer (I'm attending this years ASP.NET conference and am writing from hotel room of Mandalay Bay in Sin City, actually), and am so impressed with the Microsoft guys responsible for this technology -- Scott Guthrie, General Manager with the Microsoft Developer Division especially. This guy works hard for the betterment of the community - check out his blog on .NET technologies (ASP.NET especially). <a class="user" href="http://weblogs.asp.net/scottgu/">http://weblogs.asp.net/scottgu/</a> The ATLAS, now MS AJAX framework development goes to show how Microsoft is integrating with the developer community to get things out the door quickly in a way never seen before.And yes, the VS 2005 development environment is unrivaled...
mrteaNov 8, 2006
Will there be some sort of patch for visual studio to program for it, or will we have to go and buy a new version?
ray901Nov 8, 2006
@theonesteve "While .NET apps may cause the issues you've mentioned, can you really say Java apps don't?'One big issue I have with java is that if you want to distribute your app and don't have time/resources to WASTE on support - then you had better ship it with it's own JVM. Which is not a problem per se, ('cept the huge download size - particularly on Linux).The problem comes when the user runs more than one java app, these apps then each run in their own VM, resulting in massive bloat.
zonk3rNov 8, 2006
And your point is what exactly? Just because they haven't released one for 2.0 doesn't reflect anything on the 3.0 code.If your point was somehow that each version was getting progressively better then I'd have to point you to their history of OS development and the number of and number fixes in each service pack that have been released for each version released has ballooned. But I guess that has no reflection on MS's general level of released quality code to you.So what was your point exactly?
giginNov 9, 2006
Finally!!.. now it is important to find good learning resources. Here is one.. <a class="user" href="http://www.xamldev.com">http://www.xamldev.com</a> .Great resource to Learn WPF
thushanNov 9, 2006
*sigh*Any language you write in .NET goes down to MSIL (Intermediate Language - the Assembly language of the managed .NET environment) which then gets JIT'd (Just In Time compiled) when you run the EXE.But but but but siir... isnt that what Java does already? Yes son, it does do that but Java uses Byte code, which isnt quite as readable as IL is. The Java platform has only one language, Java, whereas .NET can support any number of languages that stick ot hte rules defined by the CLI.So essentially, if you write a .NET Application, it will get JIT'd cached, or alternatively you can use the NGen tool to avoid that process and have an almighty orgy of JIT'ing for all your signed .NET assemblies.
dotnetskyNov 10, 2006
Is that why ASP.NET is now used daily by more than 2 million professional developers worldwide, and that it runs some of the most successful websites and applications in the world, including the most heavily visited site on the web today: MySpace.com (which now handles more than 1.5 billion page views each day using ASP.NET 2.0). Not that I'm a big MySpace fanboy, but "fair is fair", pal.
agsmithNov 11, 2006
Get a clue. What .NET .EXEs are you talking about? The MSIL gets JIT compiled to native code. Run the same app a couple of times and you will notice that it gets faster and faster - because it gradually gets compiled to native code.A totally different issue is if some idiot drag & dropped some crap together and his app has 50000 wizard-generated lines of code.