Have Geek Brain

Can you upgrade to Asp.NET 4.0 now?

Ok today, as most of you have noticed that Framework 4.0 has been released. I have been working on a project that builds on the 3.5 platform. As I want to use dynamic keyword and most of asp.net features like Menu Control without keyboard, ClientIDMode and pure web.config etc. I prefer to port the unfinished project to 4.0, but I doubt it a little. Sometimes I think it's better to wait for SP1.

So what do you think about this? You guys will move on to unfinished projects or will still be coming out with 3.5 for a while.

Thanks.

+2


source to share


3 answers


The .Net 4.0 runtime has been down for a while (of course you are not RTM, but RC1, etc.). A lot of people have tested it and I guess almost all of the bugs were shocked. There should be no switching issues at this point. They have introduced a number of elements that enhance .Net. Whether you need them or not, but they can make programming in .Net easier.

You can always download 4.0 locally and test it on your project. Worse, it gets worse, the project explodes and you reload it from your source control.



What you should be aware of is that there are violations in the C # and VB.Net runtime in 4.0 environment. You need to keep an eye on them.

+6


source


Probably the following applies to most basic designs.



  • Do the new features save you more time than fixing old things that happen when you upgrade?

    If you spend a lot of time getting old things to work, you might be better off just sitting on 3.x and a pre-4.x port at a later stage.

    If you really want features from 4.0 and have to spend time implementing them yourself, this might be a time-saver online.

  • Can you support this version of the framework? (i.e. can your server handle updates and keep track of everything ok?)

    If your server devices can't do this job in the field, let go now. I don't know your organizational structure or who runs your servers, but I do know that some companies have a pretty thorough testing regime, they will run the software before allowing it. As a brand new version, they can be tired.

    And let's be frank, just because something goes through multiple previews, they won't catch every bug because they're rarely used in production scripts. You know what to do.

    And if installing 4.0 on the server ruins old things, you might wait a long time.

  • Perhaps your project will be launched after the first round of bug fixes?

    If you've been developing this for 3+ months you probably have plenty of time to sort through platform issues, fix code issues, and get database bugs reported with the (blind) hope that they'll fix them, or you can protect them safely.

    If you launch tomorrow, there isn't enough time to test it.

+2


source


I will only update when needed. For example, I have one application that needs to use the features provided in .Net Framework 4. This way the application will be updated as soon as possible.

I have another app, which is 3.5, without the need for driving to update at this time. This will be updated if time and budget permits.

+1


source






More articles:


All Articles