A
Ajith Menon
I am working on a project "ABC" which needs to be upgraded from .NET
framework 1.1.
We are thinking about upgrading it to .NET framework 2.0. The reason
for this is that we have some unmanaged modules (made in VC++) shared
with other project "XYZ". The project "XYZ" is upgraded to .NET
framework 2.0 from .NET framework 1.1.
Now to have the compatibility, forcibly project ABC also have decided
to upgrade to .NET 2.0. But I feel why not directly upgrade to .NET
3.0.
Can anybody tell me in doing this:
1. What advantages do I have in .NET 3.0 over .NET 2.0
(a. project is a windows application,
b. largely using XML files and no SQL databases.
c. It has controls like Tree view and data grids being using
extensively.
d. Lot of interaction with unmanaged code is also expected)
2. Is it error prone if I use an unmanaged code compiled using .NET 2.0
in our project which is going to be in .NET 3.0? If yes what kind of
errors may I have to face?
Regards,
Ajith
framework 1.1.
We are thinking about upgrading it to .NET framework 2.0. The reason
for this is that we have some unmanaged modules (made in VC++) shared
with other project "XYZ". The project "XYZ" is upgraded to .NET
framework 2.0 from .NET framework 1.1.
Now to have the compatibility, forcibly project ABC also have decided
to upgrade to .NET 2.0. But I feel why not directly upgrade to .NET
3.0.
Can anybody tell me in doing this:
1. What advantages do I have in .NET 3.0 over .NET 2.0
(a. project is a windows application,
b. largely using XML files and no SQL databases.
c. It has controls like Tree view and data grids being using
extensively.
d. Lot of interaction with unmanaged code is also expected)
2. Is it error prone if I use an unmanaged code compiled using .NET 2.0
in our project which is going to be in .NET 3.0? If yes what kind of
errors may I have to face?
Regards,
Ajith