What does <project> is obsolete mean?

Posted by dangerisgo on Stack Overflow See other posts from Stack Overflow or by dangerisgo
Published on 2010-04-08T18:38:22Z Indexed on 2010/04/08 18:43 UTC
Read the original article Hit count: 417

Filed under:
|

My batch build has a project, lets call it 'My.Project'. That project got up-reved to .NET 3.5 (from .NET 1.1) in its own standalone project (meaning its not part of this batch build). Most of it is the same, there are calls that were upgraded, features added/removed. I go to start replacing all calls that all the other projects use to that, now old, project with new calls. I first remove the old reference and then add the new one. One of my projects only has one call. When I go to make the changes, one namespace in the new project throws a 'My.Project.Namespace1 is obsolete' while another call to that project throws nothing. Is there something I should be looking for? What would be causing this?

© Stack Overflow or respective owner

Related posts about obsolete

Related posts about c#