Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
DotNet
acad.assignment.mngr
academic
adonet
aspnet
aspnet.announcements
aspnet.build.controls
aspnet.caching
aspnet.datagridcontrol
aspnet.mobile
aspnet.security
aspnet.webcontrols
aspnet.webservices
clr
compactframework
component_services
datatools
distributed_apps
drawing
faqs
framework
framework.wmi
general
internationalization
interop
languages.csharp
languages.jscript
languages.vb
languages.vb.controls
languages.vb.data
languages.vb.upgrade
languages.vc
languages.vc.libraries
myservices
odbcnet
performance
remoting
scripting
sdk
security
setup
vjsharp
vsa
webservi.enhancements
webservices
windowsforms
windowsforms.controls
winforms.databinding
winforms.designtime
xml
  
 
date: Tue, 9 May 2006 22:32:29 -0500,    group: microsoft.public.dotnet.faqs        back       


Rewrite ...   
This post is mostly for discussion. Why rewrite in .NET? Just a general
discussion not related to any specific details. I was just looking to see
what reasons developers are looking to, to help decide whether they should
rewrite their app in .NET.

What are the trends being observed of Microsoft when it comes to .Net?

How much longer will COM objects live on?

How stable is the Framework?

If the goal is to maintain a software package for the next 10 years, would
that make a differnce on the decision?

What if a rewrite would take approximately 2 years, would that affect when
you decided to do a rewrite?

Are their any security benefits?

I am looking for opinions, but also links to facts that can help support
your case. I'm hoping this can become a good discussion.

Thanks
date: Tue, 9 May 2006 22:32:29 -0500   author:   Stan Canepa

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us