Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Why we have "node" as filename Nethereum.TestRPCRunner ->TestRPCEmbeddedRunner.cs, line 29 #1

Open
Kannas24 opened this issue Sep 19, 2017 · 1 comment

Comments

@Kannas24
Copy link

Kannas24 commented Sep 19, 2017

I don't think this is a running project, I'm testing it on Visual Studio 2017 and at line 37, in "Nethereum.TestRPCRunner ->TestRPCEmbeddedRunner.cs" file it throws an error.

Error : "The system cannot find the file specified"

When I change the fileName property to point to the .tmp file (where we are saving .js file data), it says "The specified executable is not a valid application for this OS platform.". It sounds to me that "node" is a command which we are supposed to use and .tmp file name with arguments are the options we should pass, please confirm.

Note: I'm from c# background and new to ETHEREUM. Instead of trying things with node.js and stuff I would prefer to use c#/.net to learn ethereum dapp application implementation.

@juanfranblanco
Copy link
Member

juanfranblanco commented Sep 19, 2017

@Kannas24

There is a dependency with node as TestRpc is written in javascript. The Testrpc runner has been created to allow you to create many different tests and scenarios which can launch testrpc.

The dependency will be able to be removed when Nethereum (eventually) implements a full Ethereum test client.

For the time being, I suggest you use geth for testing if you don't want to depend on node / javascript. You can use the Clique, Proof of Authority which has a much faster consensus algorithm and simplifies testing.
https://github.com/Nethereum/Nethereum/tree/master/testchain/clique

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants