• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 857
  • Last Modified:

Target framework verion different?

Hi,

I have several vb.net projects which are referencing .net 2.0 and I created projects using .net 3.5 and 4.

When I try to reference newly created projects to the old project, I am getting this message.

I would like to upgrade old projects to the net 3.5 or 4.

Do I just unreference thos .net2.0 and add .net3.5?

How can I check if current app will break or not with more recent framework?






The Target Framework version for the project 'XXX.Gui' is higher than the current project Target Framework Verion
Would you like to addthis refrence to your project anyway?
0
dkim18
Asked:
dkim18
3 Solutions
 
CodeCruiserCommented:
You can change the framework version in project properties.
0
 
Jacques Bourgeois (James Burger)Commented:
Most of the time, using the newer version of the framework is better. Performance can be improved, rare bugs could have been solved, new features might have been added. As long as the users have the newer version of the framework installed on their computer that is.

There are very few breaking changes between versions of the framework, and those usually involve features that are used by a very small percentage of programmers.

And Microsoft uses a very good way of making changes to the framework. They never intentionnally make changes that will break applications right away. The thing works very well if you do not skip a version of the framework. Advised programmers always check their projects regularly in the free Express Edition of Visual Studio when they need to skip a version, so as to make sure that the following mechanism works for them.

When they need to change something that can break old applications, they leave it in the newer versions of the framework for a few years. It's use shows a warning, so it can still be used for 1 or 2 versions of the framework. You also get a link to a way to prepare your project for the day the feature will be definitively removed or changed. So, when you upgrade a project from one version of the framework to the one or two that comes just after, you are told of future breaking changes.

Take the attached screen shot. This warning appears in code that targets framework 4 and 4.5. Eventually, in later frameworks, it will become an error. But programmers who check their project regularly against the latest version of the framework, even if they are still on 3.5 for some reason, have known for 2 years now that OracleClient will eventually be dropped, and they are already coding with that warning in mind so their application won't break when they will switch to a version of the framework that does not support Oracle from the box.
OracleClientAnnouncedDeath.jpg
0
 
Jaime OlivaresCommented:
There is no problem when referencing a difference .net version in the range 2.0 - 4.5. This is just a [good] suggestion to take into account.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now