My Current Learning List of Technologies

Gil Fink — Sun, 11 Jan 2009 21:07:08 GMT

My Current Learning List of Technologies

In the last few days I have started to learn
few old/new technologies that I think you
should consider learning in the near future
as well (if you didn’t learn them before).
The technologies:

ASP.NET MVC Framework – the new framework that
leverage the MVC pattern for ASP.NET. The technology
is a must learn technology for every .NET web developer in
my opinion. Learning the framework will give you a new
choice for implementing web applications with MVC pattern instead of
web forms. A lot was written in the area of ASP.NET MVC and I urge you to
go and explore the framework. The framework is going to be available side
by side with web forms and you’ll have the choice of using one of them or
using other non Microsoft web development framework.
Microsoft Sync Framework – the new Microsoft synchronization platform.
The Sync Framework helps to build sync ecosystems that will be able to
integrate any application (web, win, mobile and etc) with any data from
any store using any protocol over any network. for more details about the
framework you can read my previous post - Getting Started with Microsoft
Sync Framework.
NHibernate – I have always wanted to learn the NHibernate ORM in order to
compare it with Entity Framework or LINQ to SQL. Until now I haven’t had time
for this but lately I started to learn the framework and I enjoy it a lot.
I urge you to learn the framework in order to have more choices when you are
searching for a ORM solution. A very good place to start is the summer of
NHibernate screencast series.

In the near future I’m going to write about these subjects so stay tuned.
Which technologies you think that developers should consider learning in the near
future?

The End of LINQ To SQL?

Gil Fink — Fri, 31 Oct 2008 15:20:04 GMT

The End of LINQ To SQL?

Today I read a few
blog posts that were
published regarding
the announcement
on the ADO.NET Team Blog
(David Hayden, Oren Eini
and more).
That announcement included the following lines which made everybody furious:
”We’re making significant investments in the Entity Framework such that
as of .NET 4.0 the Entity Framework will be our recommended data access
solution for LINQ to relational scenarios. We are listening to customers regarding
LINQ to SQL and will continue to evolve the product based on feedback we receive
from the community as well.”.
I share the same thoughts as David Hayden expressed in his post. I think that if
Microsoft is going to abandon LINQ to SQL, they should publish the framework on
CodePlex and let the community continue the development effort.
This way the people that started using LINQ to SQL in the last year
will have a support for that framework and won’t have to change all their data
access because the framework is legacy. Also, LINQ to SQL will continue to be
a light weight alternative to the Entity Framework like other open source frameworks
(NHibernate, SubSonic, Castle ActiveRecord and more).
If you think like the other community members and also like I do, write about it and
show that you care.

Gil Fink's Blog : DEV, LINQ to SQL

My Current Learning List of Technologies

My Current Learning List of Technologies

The End of LINQ To SQL?

The End of LINQ To SQL?