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

Add ASP.NET MVC and WebAPI API reference #90

Closed
supernova-eng opened this issue Mar 6, 2018 · 15 comments
Closed

Add ASP.NET MVC and WebAPI API reference #90

supernova-eng opened this issue Mar 6, 2018 · 15 comments
Assignees
Labels
content Issue with content on docs.microsoft.com transferred Issue was transferred somewhere else.

Comments

@supernova-eng
Copy link
Contributor

The API reference for MVC and WebAPI is still only available on MSDN, not on the "docs" site.

https://docs.microsoft.com/en-us/aspnet/api-ref

Ideally, they should also be integrated into the API Browser.


⚠ Idea migrated from UserVoice

Created By: Richard
Created On: 2017/11/20 15:51:06 +0000
Votes at Migration: 2
Supporters at Migration: 2

@dend
Copy link
Contributor

dend commented May 17, 2018

@Rick-Anderson @danroth27 are there any plans to move those over?

@dend dend added triaged content Issue with content on docs.microsoft.com labels May 17, 2018
@Rick-Anderson
Copy link
Contributor

I think these will be moved but maybe not to API Browser right away.

@mschulz-msft is ASP.NET MVC 4 Reference and
ASP.NET Web API Reference being moved.

@Powerhelmsman
Copy link
Collaborator

@mschulz-msft Can you answer the question from Rick?

@dend
Copy link
Contributor

dend commented Jun 21, 2018

If that is managed reference, we need to make sure we integrate it in the API Browser.

@danroth27 @Rick-Anderson do you know where we can get the NuGet packages/assemblies for the above?

cc: @mschulz-msft

@danroth27
Copy link

@dend The packages are all on nuget.org. @dougbu or @mkArtakMSFT can provide the exact list of packages and versions.

@dougbu
Copy link

dougbu commented Jun 21, 2018

The list of ASP.NET packages we have recently updated is:

  • Microsoft.AspNet.Cors v5.2.6
  • Microsoft.AspNet.Mvc v5.2.6
  • Microsoft.AspNet.Razor v3.2.6
  • Microsoft.AspNet.WebApi v5.2.6
  • Microsoft.AspNet.WebApi.Client v5.2.6
  • Microsoft.AspNet.WebApi.Core v5.2.6
  • Microsoft.AspNet.WebApi.Cors v5.2.6
  • Microsoft.AspNet.WebApi.HelpPage v5.2.6
  • Microsoft.AspNet.WebApi.Owin v5.2.6
  • Microsoft.AspNet.WebApi.OwinSelfHost v5.2.6
  • Microsoft.AspNet.WebApi.SelfHost v5.2.6
  • Microsoft.AspNet.WebApi.Tracing v5.2.6
  • Microsoft.AspNet.WebApi.WebHost v5.2.6
  • Microsoft.AspNet.WebPages v3.2.6
  • Microsoft.AspNet.WebPages.Data v3.2.6
  • Microsoft.AspNet.WebPages.OAuth v3.2.6
  • Microsoft.AspNet.WebPages.WebData v3.2.6
  • Microsoft.AspNet.WebPages v3.2.6
  • MvcDiagnostics v5.2.6

Not sure if it matters in this context, but we've updated locale-specific packages for all of the above that have them.

@dend
Copy link
Contributor

dend commented Jun 21, 2018

@danroth27 @dougbu thanks, this looks good. Should all these be classified as "ASP.NET MVC5"?

@danroth27
Copy link

These are collectively the packages for ASP.NET MVC, Web API and Web Pages. They typically all ship together but they are separate frameworks with separate versions. We should probably spit them.

ASP.NET MVC 5.2
Microsoft.AspNet.Mvc v5.2.6
MvcDiagnostics v5.2.6

ASP.NET Web Pages 3.2
Microsoft.AspNet.WebPages v3.2.6
Microsoft.AspNet.WebPages.Data v3.2.6
Microsoft.AspNet.WebPages.OAuth v3.2.6
Microsoft.AspNet.WebPages.WebData v3.2.6
Microsoft.AspNet.WebPages v3.2.6
Microsoft.AspNet.Razor v3.2.6

ASP.NET Web API 5.2
Microsoft.AspNet.WebApi v5.2.6
Microsoft.AspNet.WebApi.Client v5.2.6
Microsoft.AspNet.WebApi.Core v5.2.6
Microsoft.AspNet.WebApi.Cors v5.2.6
Microsoft.AspNet.WebApi.HelpPage v5.2.6
Microsoft.AspNet.WebApi.Owin v5.2.6
Microsoft.AspNet.WebApi.OwinSelfHost v5.2.6
Microsoft.AspNet.WebApi.SelfHost v5.2.6
Microsoft.AspNet.WebApi.Tracing v5.2.6
Microsoft.AspNet.WebApi.WebHost v5.2.6
Microsoft.AspNet.Cors v5.2.6

@mschulz-msft
Copy link

Sorry for the late response, somehow this just hit my inbox.

We moved some ASP.NET docs from MSDN to docs.microsoft.com/previous-versions as part of the migration project. The migrated content can be found here: https://docs.microsoft.com/en-us/previous-versions/aspnet/

If there is other content not captured in the above and still on MSDN, we need to add it to the backlog for the move ASAP.

@dend
Copy link
Contributor

dend commented Jun 22, 2018

@danroth27 great, thanks! This should give us a starting point.

@Powerhelmsman
Copy link
Collaborator

The issue is transferred to vsts-rest-api team. They will help there. I will close as transferred. If you have other question related to this issue, we can reopen it and continue discussion.

@dend dend reopened this Jun 29, 2018
@dend
Copy link
Contributor

dend commented Jun 29, 2018

@Powerhelmsman this is not REST. This is a request to onboard .NET-based APIs to docs.microsoft.com. I will take care of this and close the issue once we have the APIs onboarded.

@dend dend assigned dend and unassigned Rick-Anderson Jul 4, 2018
@Powerhelmsman Powerhelmsman removed the transferred Issue was transferred somewhere else. label Jul 5, 2018
@dend dend added the in-progress Work started on the item! label Aug 31, 2018
@dend
Copy link
Contributor

dend commented Aug 31, 2018

A good chunk of the ASP.NET MVC content is in this PR: dotnet/AspNetApiDocs#81. We will continue working on shipping the rest soon.

For reference, we will redirect content from MSDN.

@dend
Copy link
Contributor

dend commented Oct 31, 2018

@dend dend closed this as completed Oct 31, 2018
@danroth27
Copy link

Thanks @dend!

Did the ASP.NET Web API docs get added? I only see MVC and Web Pages listed . . .

image

@Powerhelmsman Powerhelmsman added the transferred Issue was transferred somewhere else. label Nov 3, 2018
@Powerhelmsman Powerhelmsman removed the in-progress Work started on the item! label Nov 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Issue with content on docs.microsoft.com transferred Issue was transferred somewhere else.
Projects
None yet
Development

No branches or pull requests

7 participants