System.* not defined or imported

Pieter Claassens

Good afternoon,

a bit stumped with this one - any help would be greatly appreciated:

System.Void, System.Object, System.Inptr not defined or imported... a little bit stumped with this one... any help would be greatly be appreciated...

Regards,
Pieter Claassens

Lost User

As you have been told repeatedly, a couple of words, taken out of context, does not give enough information to know what the problem is. Please show the actual code you are using and explain what you are trying to do.

Pieter Claassens

Hi, Here is a sample exceprt of the code prudicing the erorr message :

public delegate void CallbackType(bool success, TReturnType returnValue);

Quite a lot of errors/warnings for a one-liner...

Lost User

What is CallbackType, what is TReturnType. And did you write this code or are you trying to use something that someone else has written. As I keep saying, please show the full context, that means the code whare the erro(s) occur, and the actual error message(s). A single line out of context, with no accompanying detail, is still not enough. You may know what is showing on your screen terminal but we cannot see it.

Richard Andrew x64

Maybe he's paranoid and doesn't want anyone to see his code. Hence the obfuscation of the types.

The difficult we do right away... ...the impossible takes slightly longer.

OriginalGriff

To add to what Richard has said, the cause of a syntax error isn't always where the compiler reports a problem - it may be in lines before or even after the report! For example, an additional "}" can cause some odd errors because the class and / o9r namespace has ben "closed" as far as the compiler is concerned, and it doesn't "know" what to do with your code that follows it. So when you try to report a problem to us, you need to give us more than just one line and an error message - we need context for that and that means maybe a dozen lines either side. This may help: 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! And spending a little time learning to understand syntax error messages will save you a huge amount of time in future: you waited at least 1/4 hour for Chris to reply, then your email system probably added another 10 minutes or so, plus the time it took you to type up the question once you had found this site and created an account. Chances are that you could have saved a significant chunk of that time if you knew how to read them! I'm not saying we don't want to help you fix them - sometimes I can't see my own errors because I read what I meant to write - but fixing syntax errors 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!

"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!

Lost User

Actually I think there is a much simpler answer.