Some .net-framework interfaces and attributes become obsolete and deprecated since new framework version appears. I am warned that such code may be removed or become unpredictable in next versions but
I wonder that the obsolete attribute is checked at only runtime? Think that you have two assemblies. Assembly A uses a method from Assembly B. After that we mark the method in Assembly B as obsolete
I\'m using Visual Studio 2010. But find开发者_如何学Go that the Obsolete attribute doesn\'t cause any compiler warning (I want it to cause a compiler warning).
If have a new project (ProjNew ) where I want to put several classes that are on other project (ProjOld).
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).
I\'ve read on Stack Overflow that some C functions are \"obsolete\" or \"should be avoided\". Can you please give me some examples of this kind of function a开发者_开发知识库nd the reason why?
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references,or expertise, but this question will likely solicit debate, a
I have a class that uses filesystem entities to manipulate data.We have several methods specifically designed to (attempt to) cope with some of the issues we face with this approach (file locking, non
As we approach the 4th major release of the .NET framework we are likely to see an increase in the number of classes and methods marked as obsolete (to indicate they are deprecated). I found this page
加载中,请稍侯......