J
Just D.
All,
I know that I can install 1.1 AND 2.0 on same machine at the same time, I'm
working in the VS 2003 with my aspx projects and it works great even having
2.0. I'd like to install VS 2005 to migrate to 2.0, I guess that the VS2003
and the VS2005 can coexist on the same machine and work maybe not at the
same time but one by one.
The question is: we're having a production web server with our aspx projects
working under 1.1. If we install 2.0 on this server does it break anything
and the working apps will never run again? Or IIS is able now to understand
itself if this project should work under 2.0 or 1.1 and use the appropriate
version of .NET?
Since we're having several projects working on the same server under 1.1 is
it too risky to install 2.0 on this machine? Then how can we migrate from
1.1 to 2.0? The way when we migrate step by step, app by app, is the most
preferable way to go.
Any recommendation, own experience?..
Thanks,
Just D.
I know that I can install 1.1 AND 2.0 on same machine at the same time, I'm
working in the VS 2003 with my aspx projects and it works great even having
2.0. I'd like to install VS 2005 to migrate to 2.0, I guess that the VS2003
and the VS2005 can coexist on the same machine and work maybe not at the
same time but one by one.
The question is: we're having a production web server with our aspx projects
working under 1.1. If we install 2.0 on this server does it break anything
and the working apps will never run again? Or IIS is able now to understand
itself if this project should work under 2.0 or 1.1 and use the appropriate
version of .NET?
Since we're having several projects working on the same server under 1.1 is
it too risky to install 2.0 on this machine? Then how can we migrate from
1.1 to 2.0? The way when we migrate step by step, app by app, is the most
preferable way to go.
Any recommendation, own experience?..
Thanks,
Just D.