Péter Major comments

Results 121 comments of


                                            Péter Major

The C++ module failed to load while attempting to initialize the default appdomain.

So if understand correctly now the problem is with AxoCover not finding the DLLs if they are not in the runner's directory? That could happen if they reference other native...

The C++ module failed to load while attempting to initialize the default appdomain.

To validate the above theory you could try to set the PATH environment variable on your machine to include the directory of your DLL, and restart Visual Studio and try...

The C++ module failed to load while attempting to initialize the default appdomain.

Could you create a minimalistic sample project for me, which I could check to reproduce the error you encounter? I never used AxoCover with mixed mode DLLs so far, so...

The C++ module failed to load while attempting to initialize the default appdomain.

(AxoCover runs tests in separate AppDomain, if this is the issue, I could try to add the setting - this might be simple or not so simple depending on the...

The C++ module failed to load while attempting to initialize the default appdomain.

Thanks, I will take a look over the weekend.

The C++ module failed to load while attempting to initialize the default appdomain.

I looked at your example, if I declare your variable like this: `static ManagedClass^ g_managed = gcnew ManagedClass();` in your class in the header, then it works properly.

The C++ module failed to load while attempting to initialize the default appdomain.

For the tests to run in VS you need a runsettings file to be specified for running in x64 mode, I used this: [runSettings.zip](https://github.com/axodox/AxoCover/files/1963300/runSettings.zip)

Could not open test file

Hmm, maybe there is a problem with reaching the specific line in the file. This is likely a bug. It could also be that the source file has been modified...

Could not open test file

I will review the affected part of the code and add some logging sometime this week. With that we should be able to get a better look at the problem....

Hmm... It seems GitHub is not supporting these kind of email attachments. You could either drag and drop it on the [Web based UI](https://github.com/axodox/AxoCover/issues/146), or send it to AxoCover [at]...