..NET isn't a development language? It is a supporting technology/framework?
Yes I have plenty of experience -- for Windows Forms applications the
migration will be pretty easy and you can choose to resolve the "Warnings"
or not when you migrate -- this is ASSUMING all your applications full under
the "managed" concept and your not using third party stuff. If you have 3rd
party controls under .net 1.1 you'll have to find out if they have a .net
2.0 control or you will need to create wrapper code to use the .net 1.1
control (one reason I no longer use 3rd party anything).
For Web applications, the code behind will be the same issues are Windows
Forms applications, however, converting an ASP.NET 1.1 web site to run
ASP.NET 2.0 web site takes more work and you have different options
available to you. Personally I'd opt for pre-compile command line for
ASP.NET 2.0 unless you have to make regulary dynamic changes daily or
weekly. You will also need to configure IIS to run ASP.NET 2.0 apps in a
separate application pool or else they will conflict with ASP.NET 1.1 web
code.
Rob
<ga**********@g mail.com> wrote in message
news:11******** **************@ i39g2000cwa.goo glegroups.com.. .
I work for a large organisation where we use .Net 1.1 as our sole
development language.
We have many frameworks and applications and web sites that are
developed in .Net 1.1
These developments are by no means trivial, they are the result of an
IT department of over 300 people and 2 years of development
It is my responsibility to develop a strategy to move to .Net 2.0, this
includes the existing applications, new developments, integration, QA,
live and development environments
Does any one have any experience in this (preferably at this scale) and
can any one recommend any reading material that would help.
Thanks
Gareth