seems to be some division of opinion about Microsoft .NET - not
least of all from the Marketing department. I was told at a MS breakfast
briefing (7 am) late last year not to expect .NET to make an impact
"for the next three to five years." On the face of it,
it appears that Microsoft just got every MS Certified Partner in
the country out of bed two hours early just to say "You can
all go back home to bed for another three to five years. Have a
croissant on the way out. Thanks for coming."
that presentation Microsoft executives outlined their vision for
the new .NET. It combines renting software over the Internet, integrating
Web documents seamlessly with each other using public, standardized
XML schemas, and enabling users to easily manipulate Web content
that has been primarily static.
the main question that developers have, is VB.NET and ASP.Net ready
now or should I keep plugging away at VB6 and ASP?
first thing to be aware of is that Visual Studio.Net is not stable
- it is pretty flakey. However the .NET Framework is stable -
this means that once you get the code written it runs fine for the
second thing to know is that code written in Beta 1 will break in
Beta 2 (especially ADO.Net database code). However this is not that
important now as Beta 2 is just about cooked. Microsoft is expected
to release 2 million copies of the second beta version of Visual
Basic.Net at its Tech Ed conference in Atlanta starting today!!!
to MS, Code written in Beta 2 will compile in the final release.
That is unless Microsoft need to change an API to fix a bug OR of
course they change their mind. So be prepared to rewrite some sections
of your code.
you need to consider deployment - ASP.NET users need only IE installed
so no hastles there if you can get the .NET Framework installed
on the server. For a lot of developers this means it is a goer.
about VB.NET you will need client workstations to have the the .NET
Framework installed to use your VB.NET executables. There will be
no .NET built into Windows until the version after Win XP (Blackcombe).
Are you prepared to have beta code on your client machines? Are
you prepared to format the client machines because there is no migration
path? For me this means VB.NET is a no goer.
you need to talk with your client on the PROs and CONs. They essentially
boil down to:
is easier to maintain - especially comparing ASP to ASP.NET
is slower to work in a beta when there are bugs and features missing.
You get to know what they are. The main problem is the lack of
documentation and a Microsoft Knowledgebase with the Bug and the
Pay Now or Pay Later? If you develop now in ASP.NET or VB.NET
instead of ASP or VB it lessens the overall cost - as you are
probably going to move the app to .NET in the future anyway.
talk seriously with your client and decide. Basically it's
OK to develop in .NET if all parties involved know and accept the
what it is worth I am not waiting for the 3 to 5 years.....
until next time,
a comment for Adam? Email Adam