strategy of migration to VS 2005

  • Thread starter Thread starter mustapha.jouad
  • Start date Start date
M

mustapha.jouad

i have like tasks to migrate an applcation (a great application , so
many packages and much design) coding in C#1.1, and i have ti migrate
it in C#2.0 (VS 2005),
i hope so for help to doing a strategy and how i can doing this work,
i m justing coming from java_world, i dont have so many experience in
DotNet;


so your comments will be the come good ,


Jouad
 
Make a copy of the Visual Studio 2003 project in a new catalogue. Open the
new project in Visual Studio 2005 and try to compile it. Tell us how things
are going.

Regards,
Lars-Inge Tønnessen
 
hi,
i want not just upgrad a old application,
but introduce new future of C#2.0 like: generic , anonymous
methode,partail classes,
for that i m in search of a strategy to doing it,
i have (150 000 ligne de code), so it s a great applications.
we want to prophit as much from this new feature.

Cordialement
Jouad
 
hi,
i want not just upgrad a old application,
but introduce new future of C#2.0 like: generic , anonymous
methode,partail classes,
for that i m in search of a strategy to doing it,
i have (150 000 ligne de code), so it s a great applications.
we want to prophit as much from this new feature.

Cordialement
Click to expand...

There is no reasonable business case for introducing new features of C# 2.0
to a working application except when fixing bugs or adding new functions
since it will add no functionality and will almost certainly create new
bugs.

You can even make a good case that it is not worth even upgrading if your
users already have the 1.1 runtime and not the 2.0 one as you will annoy
them by forcing them to install 2.0
 
i will write infrench to explain better, i hope that y speak french:
voila , c est pa juste une question d esthétique qu on veut migrer en
C#2.0, mais plutot de performance.
la genericité permit de réduire énormément la compléxité du code,
ainsi que de la réutilisation.sans prendre en compte le fait que lors
de la maitenance ca sera bcp plus facile.d 'un autre coté les "Partail
classes" qui permettent aussi de rendre le code si lissible, de
permettre le partage du code d'une meme application entre plusieurs
dévéloppeurs, surthout quand il s agit des grans projets , ce qui est
notre cas:on est mnt en 150 000 ligne de code et reste encor environ
1.5année autre pour la valider.
a coté de ca, on site les "Nullable Type" qui vont réduire du travail
et permettent de manipuler des opératoins que jadis on n'y pense meme
pas et on évite par la suite les points de controles (et donc réduire
le temps de réponse)
le "Cast& exception" vont etre si éviter dans la majorité dans
traitement, et donc un gain énorme au niveaux de l exécution et du
temps de réponse, sachant que notre application est destinée au
bourses et au bank:" http://www.quodfinancial.com", est donc la
migration s'avère si crucial pour nos métiers.


Cordialement
Jouad
 
Sorry no, I don't understad a single word French.

Best Regards,
Lars-Inge Tønnessen
 
VB6 and VB.NET are very different.

You do not migrate from C# 1.1 to C# 2.0.

Regards,
Lars-Inge Tønnessen
 
hi,
i dont understaund what do yo mean: "y do not migrate from C#1.1 to
C#2.0"


Regards,
Jouad
 
Back
Top