Home/ Questions/Q 8016577
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T20:34:34+00:00

Note: I already checked msdn, it doesn’t address my actual question, see below. I’m

  • 0

Note: I already checked msdn, it doesn’t address my actual question, see below.

I’m trying to use the obsolete attribute on a (obviously obsolete) constructor in one of my classes. Here’s the scenario:

I want to be able to force the developer to update to the new constructor without affecting already existing and deployed code. This way I can deploy my code to production just fine, but from a developers perspective, whenever they go into their code, instead of just getting a “warning” which I’m sure they’ll just ignore, I want them to get a compile error because the status quo is no longer ok.

So my question is, will this affect only developers, or all calling apps, or do I have the whole thing wrong?

sample code:

public class MyClass
{
   private string _userID; //new code

   [Obsolete("This constructor is obsolete, please use other constructor.", true)]
   public MyClass()
   {
      _userID = ""; //defaulting to empty string for all those using this constructor
   }

   public MyClass(string userID)
   {
      _userID = userID; //this is why they need to use this constructor
   }
}

Any and all help will be appreciated, thanks in advance!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Yes, this primarily affects the compiler – any pre-built code won’t be affected… unless that code explicitly checks for this attribute. For example, some serialization code (XmlSerializer, IIRC) checks for this – so it might not be entirely side-effect free… but in principal existing code won’t usually be affected until they try to compile next.

    Of course, if you are using this code from something that uses dynamic compilation (for example ASP.NET without pre-compile) then all bets are off.

    • 0