These are chat archives for Nethereum/Nethereum
Hey @rsantirso, off the top of my head transaction receipts don't produce output (only input) - so if a function (not view/pure) which does a state change, you won't be able to get the output from the transaction, hence the need for Events.
Remix does it differently since it's running on a sandboxed environment.
Am on the road right now so I'll take another look once I am home. Could you share with me your contract code please so I could take a closer look, in case I am missing anything? Thanks.
You're awesome, @EnigmaticUnreal_twitter . I'm gonna write down some tips for beginners (like me) compiled after my conversation with Enigmatic:
1- You can return values from functions but your code can't be dependent on them after transactions. It is right to get and use those returned values after Calls.
2- CallAsync doesn't rely on web3.TransactionManager, so any gas value set in the manager won't affect calls.
3- Derived from previous point, feed CallAsync with a proper gas value.