The error message is pretty explicit: there isn't a variable called
axWindowsMediaPlayer1 in the current scope.
Start by looking at the error message closely - it tells you which file the error occurred in and the line and column at which the problem was found. In Visual Studio, you can double click the error message in the Errors pane and it will take you directly to the line.
That'll show you where the reference to the variable is: now look around that code and see if you can find why that line of code is there!
And read this:
How to Write Code to Solve a Problem, A Beginner's Guide Part 2: Syntax Errors[
^] - it should help you next time you get a compilation error!
You should expect to get syntax errors every day, probably many times a day while you are coding - we all do regardless of how much experience we have! Sometimes, we misspell a variable, or a keyword; sometimes we forget to close a string or a code block. Sometimes the cat walks over your keyboard and types something really weird. Sometimes we just forget how many parameters a method call needs.
We all make mistakes.
And because we all do it, we all have to fix syntax errors - and it's a lot quicker to learn how and fix them yourself than to wait for someone else to fix them for you! So invest a little time in learning how to read error messages, and how to interpret your code as written in the light of what the compiler is telling you is wrong - it really is trying to be helpful!
Sorry, but we can't fix this for you - we have no access to your code!
I'm not saying we don't want to help you fix syntax errors - sometimes I can't see my own errors because I read what I meant to write - but fixing them is part of the job, and if you can't do it for yourself people are going to look at you as a bit weird should you get a job in the industry!
Submit an article or tip