Skip to content

NuGet package out of date #14

Open

Description

@paulbouwer

Just a heads up.

The NuGet package on NuGet (https://www.nuget.org/packages/ScriptCs.WebApi/) is version 0.1.0. The code here is at version 0.5.0.

I am getting the following error when using the NuGet package (0.1.0) and executing scriptcs start.csx:

Message: No HTTP resource was found that matches the request URI 'http://localhost:8080/api/Test'.
MessageDetail: No type was found that matches the controller named 'api'.

I don't get this error when using the code here (0.5.0) directly.

Activity

  1. glennblock commented on Mar 23, 2014

    @glennblock
    Contributor

    Hi Paul

    Don't use Api in the uri. On the version, yes I need to get it updated and
    out there.

    On Saturday, March 22, 2014, Paul Bouwer notifications@github.com wrote:

    Just a heads up.

    The NuGet package on NuGet (
    https://www.nuget.org/packages/ScriptCs.WebApi/) is version 0.1.0. The
    code here is at version 0.5.0.

    I am getting the following error when using the NuGet package (0.1.0) and
    executing scriptcs start.csx:

    Message: No HTTP resource was found that matches the request URI '
    http://localhost:8080/api/Test'.
    MessageDetail: No type was found that matches the controller named
    'api'.

    I don't get this error when using the code here (0.5.0) directly.

    Reply to this email directly or view it on GitHubhttps://github.com//issues/14
    .

  2. paulbouwer commented on Mar 23, 2014

    @paulbouwer
    Author

    Thanks Glenn. That works for me :)

    The api bit wasn't obvious since the routeTemplate in the current code base is: "api/{controller}/{id}".

  3. glennblock commented on Mar 23, 2014

    @glennblock
    Contributor

    Which code?

    On Saturday, March 22, 2014, Paul Bouwer notifications@github.com wrote:

    Thanks Glenn. That works for me :)

    The api bit wasn't obvious since the routeTemplate in the current code
    base is: "api/{controller}/{id}".

    Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-38370323
    .

  4. glennblock commented on Mar 23, 2014

    @glennblock
    Contributor

    I see it. That must have come in via a merge. By design it shouldn't be
    there since for self host there is no need for an API route. At least there
    hasn't been. With OWIN though maybe it should be API.

    On Saturday, March 22, 2014, Paul Bouwer notifications@github.com wrote:

    Thanks Glenn. That works for me :)

    The api bit wasn't obvious since the routeTemplate in the current code
    base is: "api/{controller}/{id}".

    Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-38370323
    .

  5. paulbouwer commented on Mar 23, 2014

    @paulbouwer
    Author

    Yes - I saw that it come back in one of the merges after you mentioned it
    shouldn't be there.

    On Sun, Mar 23, 2014 at 11:39 AM, Glenn Block notifications@github.comwrote:

    I see it. That must have come in via a merge. By design it shouldn't be
    there since for self host there is no need for an API route. At least there
    hasn't been. With OWIN though maybe it should be API.

    On Saturday, March 22, 2014, Paul Bouwer notifications@github.com wrote:

    Thanks Glenn. That works for me :)

    The api bit wasn't obvious since the routeTemplate in the current code
    base is: "api/{controller}/{id}".

    Reply to this email directly or view it on GitHub<
    #14 (comment)

    .

    Reply to this email directly or view it on GitHubhttps://github.com//issues/14#issuecomment-38370384
    .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions