Migrating to .NET Framework 2.0? Let us do the testing for you….


Over the next year many of you will be migrating your V1.x applications to 2.0.  This will no doubt require a testing pass to ensure your application continues to work as expected.  At the same time, we are trying hard to ensure that applications can migrate to 2.0 seamlessly.  We have a ton of test cases in house to do validation of compatibility between 1.x and 2.0, but as any good tester would tell you, there is no substitute for running the real thing.  

 

Maybe there is a deal we can reach?  Our interest is making sure v2.0 works on as wide a range of applications as possible and yours is to ensure that *your* application works on 2.0.  We’d be happy to do some level of testing of your application on 2.0 for you and fix any compat bugs in 2.0 we find in the process.  

 

Interested?  Contact Jay to get started!

 

Comments (7)

  1. . says:

    Im starting to use Oberon.NET, can 2.0 C# use a single alias for MULTIPLE library imports?

  2. . says:

    Just download 1.1 .NET code from sourceforge and test that.

  3. I wish that you won’t need to change anything and all applications work properly 😉

  4. Me too! We are doing the best we can to balance the needs of innovation and compatibility

  5. . says:

    How will this affect other languages like Oberon.NET and so on?

  6. Keith Hill says:

    >> I wish that you won’t need to change

    anything and all applications work properly 😉

    There’s always side-by-side execution of the CLR, right? No one says you have to move your app onto the latest version of the CLR. Now if you want to do that, I guess I wouldn’t mind have to do some limited amount of porting especially were I might be using either buggy or poorly designed FCL code. Over time I would like to see the FCL morph into an even better designed framework without any of the old baggage types in the way.