What should developers do TODAY to prepare for the future?


"urn:schemas-microsoft-com:office:smarttags"
/>
The other day at the Triangle Area .NET
Users Group someone asked me an interesting question.  Based
on my experience at Microsoft working on future versions on the .NET
Framework and the Windows operating system, what should developers do TODAY to prepare
for the future?  "urn:schemas-microsoft-com:office:office" />

 

I was not able to come up with anything earth shattering, but I thought I’d share
these with you.

 

1. Make the move to managed code!  I am
likely preaching to the choir here.  But
it is true, the vast majority of developer experiences coming out of Microsoft are
going to be based on managed code.  Everything
from application automation to APIs for new platform features.

That said, we continue to invest heavily in interop.  Most
of the important applications Microsoft has are unmanaged and we recognize the investment
many ISVs have in unmanaged code.  We
are NOT likely to push any kind of 100% pure managed as the only true way.  Almost
all the new stuff we are building have a way (mostly through interop) to access great
new features from unmanaged code.

 

2. Use good application architecture techniques. Factor your UI from our business
logic from your database logic.  Use XML
based web services anywhere you are communicating across organizations and consider
even in cross machine communication in the same company.  This
kind of architecture will allow you, for example, to have the option of easily changing
an ASP.NET
site to use client side front end.

 

I am sure this is just a start…

 

 

Comments (3)

  1. The Application Architecture points from point 2…are you really advocating using XML in cross machine communication within an organisation? I can see the point in this for the Business Layer -> Presentation layer communication – since you could more simple change the presentation layer, but for data access this adds huge overhead to what is generally already the most congested pipe… I guess Yukon will make this easier to do (i.e., XML as the primary data access mode) – but I don’t think most applications really need it!

  2. selina says:

    we should do full preparation for the future !we can develop all kinds of qualification to wellcom our new challengen !

  3. For some reason I started reviewing some of my friend’s Brad Abrams old Blog entries. It was one of those