Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3451940
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 18, 20262026-05-18T09:11:59+00:00 2026-05-18T09:11:59+00:00

When I declare a public event in a sealed C++/CLI class, I get Code

  • 0

When I declare a public event in a sealed C++/CLI class, I get Code Analysis warning CA1047. The warning seems to come from auto-generated protected member functions. How can I fix this warning?

Here’s an example. This code

ref class Test sealed {
public:
    event EventHandler^ blah;
};

generates:

warning: CA1047 : Microsoft.Design : Make member ‘Test::blah::raise(Object^, EventArgs^)’ private, public, or internal

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-18T09:12:00+00:00Added an answer on May 18, 2026 at 9:12 am

    I’ll document the question better. This code

    ref class Test sealed {
    public:
        event EventHandler^ blah;
    };
    

    generates:

    warning: CA1047 : Microsoft.Design : Make member ‘Test::blah::raise(Object^, EventArgs^)’ private, public, or internal

    Yes, when you don’t specify the event accessors yourself then the compiler will generate them for you. It auto-generates the add, remove and raise accessors. The latter one looks like this when you look with ildasm.exe:

    .method family hidebysig specialname instance void 
            raise_blah(object value0,
                       class [mscorlib]System.EventArgs value1) cil managed
    {
        // etc..
    }
    

    The family attribute is what causes the code analysis warning. The auto-generated add and remove accessors are of course public. Writing them yourself is a questionable workaround, you really only want to do this if you have a real reason to implement custom accessors. The boilerplate version would look like this:

    using namespace System::Runtime::CompilerServices;
    
    ref class Test sealed {
    private:
        EventHandler^ foo;
    public:
        event EventHandler^ blah {
            [MethodImpl(MethodImplOptions::Synchronized)]
            void add(EventHandler^ d) { foo += d; }
            [MethodImpl(MethodImplOptions::Synchronized)]
            void remove(EventHandler^ d) { foo -= d; }
        private:
            void raise(Object^ sender, EventArgs^ e) { 
                EventHandler^ handler = foo;
                if (handler != nullptr) handler(sender, e);
            };
        }
    };
    

    Well, that certainly suppresses the warning. I recommend you use the [SuppressMessage] attribute if that doesn’t spin your propeller.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

public sealed class FtpManager { public event EventHandler LoggingIn = delegate { }; private
The code looks like below: Clock: public class Clock { public event Func<DateTime, bool>
How to declare a static dictionary object inside a static class? I tried public
Assuming we declare a class DerivedEventArgs : public class DerivedEventArgs : EventArgs { ...
In my class I want to declare an event that other classes can subscribe
I think in this case there is no need to declare a public constructor
I noticed some people declare a private variable and then a public variable with
It's possible to declare variables with the below structure in C++ private: public: protected:
I've got the following Generic usercontrol declared: public partial class MessageBase<T> : UserControl {
Are there any reason why you should not declare an event backing field protected?

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.