Visual Studio likes to warn you when it thinks that one of your functions could be declared 'noexcept' but isn't. Annoyingly, it can sometimes do this for virtual functions which are defined in a base class to do nothing, even though a derived class might be intended to override the function to throw exceptions.
Using noexcept(false) on the base class function declaration and definition can prevent this warning from being generated. (Using "#pragma warning (suppress: C26440)" on the function definition is another approach, and one that I personally find preferable.)