AxoCover icon indicating copy to clipboard operation
AxoCover copied to clipboard

.Net core support

Open axodox opened this issue 7 years ago • 11 comments

Extend code coverage support to .Net Core projects

axodox avatar Feb 21 '17 15:02 axodox

Waiting a lot 😄

Caldas avatar Feb 21 '17 22:02 Caldas

I will try my best ;).

But I will need to go to Canada soon for a while (from Hungary, work related), so I likely have some very busy months ahead of me. That being said I wanted to signal that it is in the works and it will come sooner or later.

axodox avatar Feb 21 '17 22:02 axodox

I will comment that if it would be interesting. I had problems with an assembly that is .net standard, because it wasn't covered by the tests. This is because in the properties of the project, in build options, in the button of advanced options, the PDBs was set as portable. When I changed that to full, then the assembly was added to the results of the tests.

Perhaps with .net Core it happens the same, that you have to change the PDBs to full.

ComptonAlvaro avatar Jun 01 '17 07:06 ComptonAlvaro

@ComptonAlvaro Tried that with .NET Core and it didn't help. 😢

This is really needed, many people are now using Core...

grokky1 avatar Jun 14 '17 11:06 grokky1

@grokky1 I am sad to hear that in your case this solution doesn't work.

Anyway, if you don't need the features that .net Core has and .net standard doesn't have, you could think to port the .net Core to .net standard. Why is the reason why you want to use .Core instead of .net standard?

ComptonAlvaro avatar Jun 14 '17 11:06 ComptonAlvaro

@ComptonAlvaro Because ASP.NET Core

BTW Are you saying your trick works for others who are using Core? When I tried it (Win10, VS2017) it told me that it couldn't find any tests.

grokky1 avatar Jun 14 '17 11:06 grokky1

@grokky1 I have tried this in a .net standard project, I don't know if the trick will work or not in .net Core, it seems that it doesn't work because you have tried and it doesn't work. So an alternative it is to see if you could use a .net standard project instead of .net Core. Are you using .net Core because you will want to use the application in other operative system different to windows like linux? If not, perhaps .net standard would be a better option for you, because it will use the library in xamarin and UWP projects.

ComptonAlvaro avatar Jun 14 '17 11:06 ComptonAlvaro

Any update on this?

Also, it seems with the latest version of UWP (Fall creators update) AxoCover does not detect any tests.

jamers99 avatar Apr 10 '18 18:04 jamers99

Not much I am afraid, this would really need a considerable amount of time to do. I have started documenting the code, so if someone is willing to do it they will have the info.

axodox avatar Apr 10 '18 18:04 axodox

What about the UWP support?


From: Péter Major [email protected] Sent: Tuesday, April 10, 2018 2:46:04 PM To: axodox/AxoCover Cc: jamers99; Comment Subject: Re: [axodox/AxoCover] .Net core support (#9)

Not much I am afraid, this would really need a considerable amount of time to do. I have started documenting the code, so if someone is willing to do it they will have the info.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Faxodox%2FAxoCover%2Fissues%2F9%23issuecomment-380207146&data=02%7C01%7C%7C24283d5a4a0c45a5fe7708d59f135091%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636589827658837810&sdata=pPFNLgBLosBXbWHsczTw9eJZNIl24kgDyq4qxTxOgBc%3D&reserved=0, or mute the threadhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAT16h6DQe0RWKRjaqXwL6lMK1euUHwc7ks5tnP3sgaJpZM4MHdfD&data=02%7C01%7C%7C24283d5a4a0c45a5fe7708d59f135091%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636589827658837810&sdata=gryvavSK%2FLRbsgtyqWYJazjfxWDlKykntzPCo42oEDA%3D&reserved=0.

jamers99 avatar Apr 10 '18 18:04 jamers99

I am not working on UWP applications, so I have not tried it yet. But I guess the case UWP support is likely to be similar in its requirements - that is we cannot execute the tests in the current full .Net Framework runner as is. Some workarounds are likely possible, e.g. by moving the non-UI code to .Net Standard + build full PDB.

axodox avatar Apr 11 '18 08:04 axodox