Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Mvc 6 #53

Open
AlexArchive opened this issue Feb 11, 2015 · 5 comments
Open

Support for Mvc 6 #53

AlexArchive opened this issue Feb 11, 2015 · 5 comments

Comments

@AlexArchive
Copy link
Contributor

It would be nice to have support Mvc 6.

I am eager to try my hand at this but I recommend that we wait until:

  1. The public Api is locked down
  2. There is more documentation etc. on the build infrastructure

I suspect we'll have to change the implementation considerably in some places but I am not yet sure.

@AlexArchive
Copy link
Contributor Author

I stumbled upon a couple of posts on this subject. I am posting them here for future reference and for anyone else who may be interested:

I will post more posts that I think might be relevant as I come across them.

@robdmoore
Copy link
Member

Nice!

On 12 Feb 2015, at 1:24 am, ByteBlast [email protected] wrote:

I stumbled upon a couple of posts on the subject of upgrading to Mvc 6. I will post them here for the future reference and for anyone who might be interested.

Update on Autofac and ASP.NET vNext -An ASP.NET vNext Build and Repo Structure Braindump

Reply to this email directly or view it on GitHub.

@Tgueth
Copy link

Tgueth commented Feb 22, 2016

Any update? While API still has some flux, it does appear to be settling down. Would be interested in knowing if anyone is working on this yet.

@robdmoore
Copy link
Member

I'm happy for anyone that wants to give this a go to go for it :)

@ivaylokenov
Copy link

ivaylokenov commented Jun 9, 2016

I have implemented similar testing framework for ASP.NET Core. It is available here: https://github.com/ivaylokenov/MyTested.AspNetCore.Mvc
It is in preview state, because it needs more work but controller and route testing should work without any issue. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants