updating to framework 3.0
-
Hi folks, I am nearing the end of the first cycle of developement for my application. We began this with the .net framework 2.0, However we are now interested in using WPF and for that it appears we need to upgrade to 3.0. My question is does anyone know if migrating an application from .net 2 to 3 is a big task and would we need to undergo any major changes. Obviously at this stage we don't want to risk breaking the application too much and don't have the time to undergo any major reworking. Thanks for your time Darren Sim
-
Hi folks, I am nearing the end of the first cycle of developement for my application. We began this with the .net framework 2.0, However we are now interested in using WPF and for that it appears we need to upgrade to 3.0. My question is does anyone know if migrating an application from .net 2 to 3 is a big task and would we need to undergo any major changes. Obviously at this stage we don't want to risk breaking the application too much and don't have the time to undergo any major reworking. Thanks for your time Darren Sim
.NET 3.0 is actually .NET 2.0 + WPF, WCF, and WF (WinWF). There should be no risk at all. Even going from .NET 1.x to 2.0 isn't a big risk. Very little gets removed or deprecated (deprecation is really only a problem for future Frameworks the currently desired version). The biggest thing to consider is the user experience of taking a new dependency that has little market penetration at the moment. For example, a reboot may be required before you can even set up your product.
This posting is provided "AS IS" with no warranties, and confers no rights. Software Design Engineer Developer Division Customer Product-lifecycle Experience Microsoft [My Articles] [My Blog]
-
Hi folks, I am nearing the end of the first cycle of developement for my application. We began this with the .net framework 2.0, However we are now interested in using WPF and for that it appears we need to upgrade to 3.0. My question is does anyone know if migrating an application from .net 2 to 3 is a big task and would we need to undergo any major changes. Obviously at this stage we don't want to risk breaking the application too much and don't have the time to undergo any major reworking. Thanks for your time Darren Sim
At the microsoft launch event, the presenters said that the .NET framework 3.0 is the same as .NET 2.0 but it includes WPF, WCF, and CardSpace (might be missing a category, but still). Your applications should work fine with .NET 3.0, but if you want to take advantage of WPF then you will need to rewrite the GUI aspect of your applications using the .NET 3.0 tools. But the source code change from .NET 2.0 to .NET 3.0 should not change.
Regards, Thomas Stockwell Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. Visit my homepage Oracle Studios[^]
-
.NET 3.0 is actually .NET 2.0 + WPF, WCF, and WF (WinWF). There should be no risk at all. Even going from .NET 1.x to 2.0 isn't a big risk. Very little gets removed or deprecated (deprecation is really only a problem for future Frameworks the currently desired version). The biggest thing to consider is the user experience of taking a new dependency that has little market penetration at the moment. For example, a reboot may be required before you can even set up your product.
This posting is provided "AS IS" with no warranties, and confers no rights. Software Design Engineer Developer Division Customer Product-lifecycle Experience Microsoft [My Articles] [My Blog]
Heath! It's been a long time since you've grace the forums with your presence! We've missed your infinite wisdom in everything Windows! :-D Welcome back!
Dave Kreskowiak Microsoft MVP - Visual Basic
-
Heath! It's been a long time since you've grace the forums with your presence! We've missed your infinite wisdom in everything Windows! :-D Welcome back!
Dave Kreskowiak Microsoft MVP - Visual Basic
As you can see[^], I've been pretty busy.
This posting is provided "AS IS" with no warranties, and confers no rights. Software Design Engineer Developer Division Customer Product-lifecycle Experience Microsoft [My Articles] [My Blog]
-
As you can see[^], I've been pretty busy.
This posting is provided "AS IS" with no warranties, and confers no rights. Software Design Engineer Developer Division Customer Product-lifecycle Experience Microsoft [My Articles] [My Blog]
:omg: How many hours a day are you putting in?! Looks like my life with the Fed Government! I swear, they go out of their way to break everything they can and still call it "Production Quality". :laugh:
Dave Kreskowiak Microsoft MVP - Visual Basic
-
At the microsoft launch event, the presenters said that the .NET framework 3.0 is the same as .NET 2.0 but it includes WPF, WCF, and CardSpace (might be missing a category, but still). Your applications should work fine with .NET 3.0, but if you want to take advantage of WPF then you will need to rewrite the GUI aspect of your applications using the .NET 3.0 tools. But the source code change from .NET 2.0 to .NET 3.0 should not change.
Regards, Thomas Stockwell Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. Visit my homepage Oracle Studios[^]
Thats what I thought, but always better to be sure :) I think recreating the GUI is not an option at this stage - it's almost complete as is, and the project deadline is looming ever closer (as always). This is something I will look into further in the future, as my application is using a layered architecture it should just be a case of replacing the GUI if required. Thanks for your help guys :)
-
As you can see[^], I've been pretty busy.
This posting is provided "AS IS" with no warranties, and confers no rights. Software Design Engineer Developer Division Customer Product-lifecycle Experience Microsoft [My Articles] [My Blog]
Heath, here's a question for you. Does the /quiet switch tip also work for VS 2003 SP1?
-
Heath, here's a question for you. Does the /quiet switch tip also work for VS 2003 SP1?
Off the top of my head, no. That uses an older wrapper that doesn't support (because they didn't exist when it was written) the standard Microsoft command-line switches for update packages. You can search my blog for details.
This posting is provided "AS IS" with no warranties, and confers no rights. Software Design Engineer Developer Division Customer Product-lifecycle Experience Microsoft [My Articles] [My Blog]
-
Off the top of my head, no. That uses an older wrapper that doesn't support (because they didn't exist when it was written) the standard Microsoft command-line switches for update packages. You can search my blog for details.
This posting is provided "AS IS" with no warranties, and confers no rights. Software Design Engineer Developer Division Customer Product-lifecycle Experience Microsoft [My Articles] [My Blog]
OK. Well I've installed VS 2003 SP1 at work and it wasn't too bad. I used the /quiet trick for VS 2005 SP1. Reason I ask is because at some stage I will be applying the SPs to my home versions.
Kevin