AzamSharp

Future of .NET
published on 6/3/2008 10:00:33 PM

After listening to the DotNetRocks Podcast about the Future of .NET I asked my self what I would like to see in the future. So, I came up with my crazy list. If you think that the list did not made any sense then let me know. I can go back to the future and change it.

Downloadable Web Applications:

I know this sounds pretty crazy but with Ajax on the move this is possible. Actually, I think there are websites like PageFlakes that are coming close to being the downloadable web applications. By downloadable I don’t mean you have to wait on a webpage while the whole website is being downloaded but downloading in the form of zip file. Once, you have extracted the zip file just click on Default.aspx or Index.html and the website runs from your computer. Every request made to the server is asynchronous hence the user will have the experience that the website is installed on their machine.

Dynamic Languages:

Although this is not a future far away since IronRuby and IronPython are already in progress. I think this will give a big boost to the .NET framework. The idea of writing less code and achieving more using dynamic languages has always intrigued me.

Language Interchangeability:

Although you can use multiple languages in .NET but you cannot use different languages in the same file. Let’s say I have a .CS (C Sharp) file and I like to write VB.NET code then I would like to add a VB file. In the future I should be able to interchange VB.NET, J#, IronRuby, C# etc with each other. Also, I should have the functionality to select the code of one method and then say “Convert to IronRuby” or “Convert to J#” without having to find a tool that does the conversion.

Smart WorkFlow Engine:

Windows Workflow Engine is one of the cool technologies that can really change the way we build software. Currently, the problem with workflow engine is that it is freaking too complicated to use. Maybe in the future we can just drag and drop custom workflows on our designers and the application will be build automatically. Ohh no code generation is so evil. Well, maybe in the future it is friendly and not a demon.

Visual Studio Install Wallpaper:

We all know that Visual Studio takes lot of time to install. Off course I can go shopping or do exercise during that time but I don't like to do that boring stuff. Maybe the Visual Studio team can put Sports Illustrated Models on the install screen. Ohh yeah! that will make the install much smoother. Heck! I might uninstall Visual Studio just to see the wallpaper again!

Did you like this article?

Submit

by Mehdi Nait Yahia on 6/12/2008 1:56:25 PM
(Sorry for my limited english !!!).
i think that all the windows application will be replaced by web application usign the .NET technology.
because of
1-cost.
2- Time.
for these two points, .NET is what we need and it's the solution for the update and compatibility problem.
i'm working on an ERP project (web application)using ASP.NET and i feel the diffirence and the helpfull of this technology.

Name:
Name:
Email:
Comment/Feedback:
2+2=