Home/ Questions/Q 161341
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T11:11:45+00:00

Duplicate: Why are C# collection-properties not flagged as obsolete when calling properties on them?

  • 0

Duplicate: Why are C# collection-properties not flagged as obsolete when calling properties on them?

I just migrated a .NET 1.1 project to .NET 2.0 using Visual Studio 2008. I know that there are references to obsolete methods in the project.

But Visual Studio does not show ‘obsolete’-warnings after building. The build succeeds and shows only 3 warnings from members that are assigned a value that is never used. When I remove these members there are no warnings at all.

I NEED THESE ‘OBSOLETE’-WARNINGS

The Warning level is 4 (maximum), Warnings are enabled.

Just one sample:

protected internal DataConnector() {     _connectionString = ConfigurationSettings.AppSettings['ProductConnectionString']; }

All references that should result in an ‘obsolete’-warning are to members of classes of the .NET Framework.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Jeff Yates is right, this is a duplicate to Why are C# collection-properties not flagged as obsolete when calling properties on them?

    It is a bug in the C# 3.5 compiler reported here: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=417159

    I checked it: copied the csc.exe commandline from the output window to a cmd-console. When I change the directory to the .NET 2.0 directory (using C# 2.0 compiler), it shows the warnings. Microsoft knows this bug and fixed it in C# 4.0 but will not fix it in the 3.5 version.

    • 0