.NET vs the Competition

  • Thread starter Thread starter Jeff
  • Start date Start date
J

Jeff

I'm looking for some brief summaries or comparisons that support an IT
management decision to implement a new system with .NET and not alternative
technologies (for a client/server Windows application). Specifically looking
for things like return on investment (ROI) and total cost of ownership (TCO)
in addition to development costs, productivity comparisons, and runtime
performance.

Any links or suggestions for specific other reference material are
appreciated.
 
For basic non-mission critical stuff VS 2005 .NET 2.0 will work. But if you
want more than that go elsewhere -- I'm in the same position looking for
alternative technologies and the road MS are going on NOT where I want to be
nor most of my clients.

Rob.
 
Okay fine - I understand your point of view from your previous posts but I'm
specifically looking for ROI, TCO documentation. I know MS has it because
I've seen some of it in their presentations... just looking to get similar
 
Jeff,

ROI depends on what you want out of it -- for internal use ROI is
acceptable, for external use you will most likely have to go outside of the
"managed" solution and this is where your ROI will spiral downward -- this
is what you have to do:

1. Learn the .NET Framework 2.0 (a huge task) - documentation is better but
still missing in many areas (CR and Windows Installer)
2. If .NET framework doesn't have all you need and you opt for 3rd party
you become "unmanaged" - TCO goes up
3. Development PC's will need some serious processing power - TCO goes up
4. Debugging/maintenance is high - ROI down, TCO up
5. There will be .NET framework 2.0 updates and hopefully VS 2005 updates
as the extended BETA cycle didn't seem to make the tool any less buggy than
prior .NET versions.

I'm not sure what those BETA folks did in the long BETA cycle for VS 2005,
but clearly not many pushed the envelope or used it in real world situations
with real world customers/clients.

For real world SQL/Web development, you'll need 3 developers (interface,
middle tier, backend) and 1 graphics person and 1 DBA. 3 developers often
gets combined into 1 -- good luck with his/her sanity. Of course there are
many other issues to affect your ROI and TCO beyond just .NET.

Assumes VS 2005 and .NET framework v2.0 (language choice is irrelevant).

Rob.
 
Rob said:
For basic non-mission critical stuff VS 2005 .NET 2.0 will work. But
if you want more than that go elsewhere -- I'm in the same position
looking for alternative technologies and the road MS are going on NOT
where I want to be nor most of my clients.
Click to expand...

Just out of interest, what are problems with the framework that make you
say you are looking elsewhere? Could the framework be improved to get
your custom? As far as your comment about MS, why doesn't Win32 or a
library like MFC satisfy you?

Richard
 
Back
Top