Skip to content
This repository has been archived by the owner on Jul 9, 2022. It is now read-only.

Support for Windows IoT Core / UWP / .NET Core #3

Open
NameOfTheDragon opened this issue Jun 13, 2016 · 2 comments
Open

Support for Windows IoT Core / UWP / .NET Core #3

NameOfTheDragon opened this issue Jun 13, 2016 · 2 comments

Comments

@NameOfTheDragon
Copy link

I'm a big fan of MSpec, but that project seems to be stagnating somewhat. More seriously, MSpec has no offering for UWP and .NET Core, which means I can't use it when targeting Windows IoT Core apps, or anything based on .NET Core (ASP.Net Core, MVC Core, etc). As no-one is actively developing the framework, I'm most likely going to have to look for a different solution.

I was encouraged to learn that TestFX has a port of MSpec, but alas! No support for UWP and .NET Core. Choices are limited for UWP and .NET Core developers at the moment. Currently, only xUnit seems to have an offering. Not that xUnit is a bad choice, but I really like the MSpec style and would far prefer it.

xUnit seems to get its breadth of support by having the core types implemented as a Portable Class Library (PCL) which appears to be usable from everywhere that matters. We looked into this briefly a few days ago and it seems like it might be possible to take a similar approach for TestFX. I'm putting this issue here as a bookmark and reminder to please consider evolving TestFX to work with .NET Core and UWP.

Save me Obi Wan Kenobi, you're my only hope...

@matkoch
Copy link
Owner

matkoch commented Jun 14, 2016

@matkoch matkoch added the Core label Jun 15, 2016
@matkoch
Copy link
Owner

matkoch commented Jul 29, 2016

Referencing here too, machine/machine.specifications#296.

@matkoch matkoch added the Feature label Dec 9, 2016
@matkoch matkoch changed the title Feature Request: Support for Windows IoT Core (Universal Windows Platform) and .Net Core Support for Windows IoT Core / UWP / .NET Core Dec 9, 2016
@matkoch matkoch self-assigned this Dec 12, 2016
@matkoch matkoch removed their assignment May 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants