[C#] functions dont work on other pcs?

[ElDiabolus]

Can u answer this question: ?
Nobody could give me a valid answer before.

[Shawak]

First of all, get your signatures from pinvoke:

What do you mean with "no work"? What do they return? Can you provide some code maybe?

[th0rex]

Originally Posted by .Scy

MAYBE, just MAYBE, compile your code on the other computer before you say "it doesn't work". C# relies on the OS-libraries, as the comments pointed out, while a language like Java relies on Java-only(mostly) libraries. OS-libraries can vary alot.

go compile your code on the other computer and i bet magically it will work, since you installed the IDE that will simply provide the missing libraries OR compile the code into working byte-code.

Wtf. C# compiles to msil (AKA BYTECODE JUST FOR YOUR INFORMATION) and Java does compile to bytecode aswell. How does C# rely more on OS libraries than Java does ? BTW: The Windows API is stable and it doesn't vary alot (if they do anything, they add new functions). Please do some research before trying to help lol.

[ElDiabolus]

Originally Posted by Shawak

First of all, get your signatures from pinvoke:

What do you mean with "no work"? What do they return? Can you provide some code maybe?

The signatures are already a part of code or what do you mean?
"No work" = The functions doing nothing, but also don't release an error. It's like they weren't in code.

[Shawak]

But you are using another signature than the one from pinvoke, what does the function return?

[th0rex]

Originally Posted by .Scy

great point, java compiles to bytecode that is interpreted by the JVM, which in turn talks to the OS, so java byte code looks VERY different and obviously won't work without a JVM.

the JVM relies on system libraries, not the code a java programmer writes, most times(there are ways to interact with certain system libraries obviously).

and obviously it'd be smart to compile the code on the other PC to make ******* sure that it is not a portability problem. Stop trying to find a solution if you aren't even sure that the portability simply is the problem.

C# does exactly the same so now tell me how portability is a problem here ? And still the native function he's calling won't change its signature.

[Serraniel]

Originally Posted by .Scy

great point, java compiles to bytecode that is interpreted by the JVM, which in turn talks to the OS[...]

And MSIL ist interpreted by .Net Framework which talks to the OS (to use your words). So where is the different now?

Windows API is stable as @ pointed out already.

Another point your suggestion would fail: Compiling on another machine produces MSIL code again which has to be interpreted by the Framework which talks to the os (to describe it in your words again). So we still have 2 byte codes which may look different regarding the compiler settings, but both are indepent from the Windows Api they are compiled on...

[Dungedragon]

Originally Posted by .Scy

C# relies on the OS-libraries, as the comments pointed out, while a language like Java relies on Java-only(mostly) libraries.

C# is as platform independent as Java is by specification. Simply spoken:
C# - Code is compiled into CIL (Common Intermediate Language, also known as MSIL). Then the JIT-Compiler (Just-In-Time) compiles the code into native Code (durirng runtime) that is executed on your machine. The JIT-Compiler is part of the Common Language Runtime (CLR) while CLR (in .Net Framework) is is the implementation of the Virtual Execution System (VES) specified by the Common Language Infrastructure (CLI) Standard.
Thats a really simple summary.
Some known implementations are .Net Framework (as most famous one), .Net Native or Mono.
So telling that C# relies on OS-Librarys entirely is incorrect.

Just wanted to point that out here eventhought is does not answer the problem

[ElDiabolus]

Originally Posted by Shawak

But you are using another signature than the one from pinvoke, what does the function return?

Return is a void. What should it return?