Denis Kuzmin

Hello, Please follow the steps requested in the issue template. Nobody knows which configuration is used in your case. Also note the .line feature yet controlled by https://github.com/3F/coreclr/issues/3 in this...

Also make sure .pdb is located near final modified assembly (not original). This should be $(TargetDir)/x86 and $(TargetDir)/x64 for `x86+x64` option.

Hello, If I understood correctly, the problem may be related to the way the both processes interop using p/invoke. This may affect performance (of course) same as here: https://github.com/KirillOsenkov/Benchmarks/pull/5#issuecomment-832017735 Try...

\> If send ... from exported method (35k) and \> when .NET applicaiton load dll from P/Invoke, ... (35k) Which side is the host application for both cases? Yet again...

Hello, Unfortunately I don't understand the issue. Could you please clarify what you mean or how to reproduce the problem. Thanks.

Closed due to inactivity. Please provide further details if the problem still exists.

Hello, Make sure you are looking at a modified dll, not original. For your settings it should be inside x64 and x86 folders $(TargetDir)/x64/*.dll If not, please attach the build...

Better to reconfigure it for x64 if you only need x64. After that, the modified version will be automatically in $(TargetDir) replacing the original which Publish providers use by default....

Hello, Did you try to rebase system object? Did you check the same issue #125 ? In case to inform something new, please add more information as it says in...

Closed due to inactivity. Please provide further details if the problem still exists.