Future of Windows software development
-
Well at a Microsoft conference that I went to in November this question was asked and they presented that can be 3 ways that you can have a program for .NET. The wording is mine, I cant find my documentation from the conference. :( 1. Totally Compiled - this is like today's programs 2. JIT - the IL version gets interpreted when you run the app 3. Compiled JIT - when the app is installed it get compiled by the JIT-compiler into native code for the system and saved as the native code. This way the JIT-compiler is just run once. These ideas could have changed since November. I did not have a chance to go to the .NET talks at WinHEC since I had river talks to go to. Too bad work gets in the way sometimes. Steve Maier, MCSD
.NET programs are always compiled to IL, and then packaged in an assembly. The assembly is then installed on the customer's machine. As part of the installation process, the assembly can be "pre jitted" to native code, and this native code is cached away. This is primarily a load-time optimization, so that lots of time isn't spent in the JIT at startup time. This process is performed by a utility named NGEN. Because NGEN has less information than the normal JIT, the code that it generates has some additional indirection in it, and therefore executes a little bit slower than the normal JIT code. The NGEN translation also depends on specific machine configuration (such as security policy), and if that changes, the runtime will revert to the normal JIT. There is no totally compiled option.
-
C# primary language, thats good at least we have a target. But, where did you get the information from.
This statement came from the Microsoft guy (I've forgotten his name) who presented "Visual Studio.NET and the .NET Framework". It was also reinforced by several comments made by Jeffrey Richter last week at ".NET Developer Summit" (see http://www.microsoft.com/usa/presentations/ms.asp - select Midwest) Hope this helps. To me - it looks like IL and C# are VERY closely related. They both represent the same object model.
-
Hello, the codegurus around the world. I think that this is simple. After Microsoft throws away C++ compiler, COM and Win API, what means? Make Windows dead! As long as DOT NET is a standard enviornment, Microsoft is a king. Microsoft knows this very well since Windows dominate OS market of PC home user. Probably, Microsoft will target the company enviorment since it has the broadband. PC home user still needs Windows if we don't have a stable broadband. So, for a little while, Windows is still alive.:rolleyes: Have a nice day. -Masaaki Onishi-
-
But .NET will be an excellent choice for stand alone application development. MFC is history - WinForms is the future.
-
I've heard that Word will become .Net, and you will have to subcribe. Office XP will be integrated with .Net. As for SQL Server, and industrial strength app, I can see them having to speak to the system. I've seen some great articles about IOCP recently on the Code Project, but fail to see how .NET will deliver this kind of performance, as it acts as a wrapper for the system below.
some dot net version of sql server is in the make and on its way ;)