Matt
Sounds like you might be trying to run before you can walk. So take this slowly . . . I'm not quite sure what stage you're at, so start at the beginning (with apologies if the first 2 or 3 points are too basic).
1. I presume you've created a C# Windows Console application in some version of Visual Studio
2. Have you got a Hello World application to work? If not, see:
http://msdn.microsoft.com/en-us/library/k1sx6ed2(v=vs.71).aspx[
^]
and get the up and running.
3. Now start replacing the
System.Console.WriteLine("Hello World!");
line between the braces
{
}
with your code.
Suggest you do this adding one / a few lines at a time.
At each stage, compile it, sort out any problems, test that it does what you expect, debug it before moving on.
Make sure you understand EXACTLY what every single line does - even every character - computers have the delightful / infuriating habit of doing exactly what they are told - to the letter - neither more nor less - even the best can get caught by what, with hindsight, are trivial errors.
4. See Richard MacCutchan's solution
You have things like:
Console.WriteLine("diverName");
but then nothing to Read in any input from the user. If you don't tell the computer to read some input, it won't.
5. Looking at your compiler errors - possible mistaken empty statement
if (difficulty <= (0.9) || difficulty >= (1.68)) ;
The semicolon at the end is wrong. 'if' either has a single statement or a block of statements in braces
if(condition) statement;
if(condition)
{
statements
}
6. Use of unassigned local variable 'difficulty' (and others similarly)
Same line as above - you are using the variable called 'difficulty' before you've assigned a value to it. You've declared it near the top - but until you assign some value to it you can't meaningfully use it. See my point 4. above - I think you mean to Read a value into it from the Console.
Remember - those compiler errors are there to help you - they often aren't exactly in plain English, but can (usually) be worked out with a bit of thought and effort. They should give you the line number that's causing the problem (or sometimes the following line which can be confusing) and often the character on the line. Visual Studio tends to be very good at helping you locate the problem point in your code (double-click the error message!). For more help you can also click the error message and then press F1 to get context help on that specific error - which may explain what the problem is. failing that, Googling the error message can be enlightening.
If after all that you hit an error that really has you stumped, post a question here, with the code, the error and details of which line is causing the error.
Best of luck!