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 support for pure .net 5.0 #1906

Closed
mikeblakeuk opened this issue Nov 19, 2020 · 7 comments
Closed

Add support for pure .net 5.0 #1906

mikeblakeuk opened this issue Nov 19, 2020 · 7 comments
Labels
responded Responded with solution or request for more info

Comments

@mikeblakeuk
Copy link

In DevOps:

pool:
  vmImage: windows-latest

dotnet info #contains 3.1 and 5.0
install just dotnet 5.0
dotnet info #contains only 5.0

cproj contains:

    <Exec EnvironmentVariables="SwaggerGeneration=True" Command="dotnet swagger tofile --output $(OpenApiPath) $(TargetPath) 1.0" />

then ruining swagger gives

Tool 'swashbuckle.aspnetcore.cli' (version '5.6.3') was restored. Available commands: swagger
  
  Restore was successful.
  It was not possible to find any compatible framework version
  The framework 'Microsoft.AspNetCore.App', version '3.0.0' was not found.
    - The following frameworks were found:
        5.0.0 at [C:\hostedtoolcache\windows\dotnet\shared\Microsoft.AspNetCore.App]
  
  You can resolve the problem by installing the specified framework and/or SDK.

tools has

{
  "version": 1,
  "isRoot": true,
  "tools": {
    "swashbuckle.aspnetcore.cli": {
      "version": "5.6.3",
      "commands": [
        "swagger"
      ]
    }
  }
}
```json
@mikeblakeuk
Copy link
Author

(note; warning NETSDK1138: The target framework 'netcoreapp3.0' is out of support and will not receive security updates in the future.)

@domaindrivendev
Copy link
Owner

I believe this may be resolved with latest master. Could you try pulling down the preview Nuget from myget.org and let me know if it works?

@mikeblakeuk
Copy link
Author

@domaindrivendev
Copy link
Owner

I’m aware of the warning but your original post shows an issue - does this still occur with the latest preview build

@mikeblakeuk
Copy link
Author

The issue has gone away but only because the DevOps Agents now come with 3.1 AND 5.0 by default.
I will try and only install 5.0 later

@domaindrivendev domaindrivendev added responded Responded with solution or request for more info and removed waiting for response labels Jan 17, 2021
@domaindrivendev
Copy link
Owner

Closing due to inactivity

@mikeblakeuk
Copy link
Author

Looks like https://github.com/MicrosoftDocs/azure-devops-docs/issues/9690 is now fixed so not a problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
responded Responded with solution or request for more info
Projects
None yet
Development

No branches or pull requests

2 participants