Changeset added bin\debug for loading WebApiProxy.Tasks.dll #85

Activity

1. onionhammer

   added

   bug

   on Feb 19, 2016
2. faniereynders

   added a commit that references this issue on Feb 25, 2016

   fixing #85 bug when generating using ps script

   6b8e597
3. faniereynders

   closed this as completedon Feb 25, 2016
4. faniereynders

   reopened this on Feb 25, 2016
5. faniereynders

   closed this as completedon Feb 25, 2016
6. onionhammer commented on Mar 1, 2016

   

   onionhammer

   on Mar 1, 2016

   CollaboratorAuthor

   More actions

   Now I'm getting this

   PM> WebApiProxy-Generate-CSharp
   Cannot bind argument to parameter 'Path' because it is null.
       + CategoryInfo          : InvalidData: (:) [Add-Type], ParameterBindingValidationException
       + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.AddTypeCommand
       + PSComputerName        : localhost
   
   Unable to find type [WebApiProxy.Tasks.Models.Configuration]. Make sure that the assembly that contains this type is loaded.
       + CategoryInfo          : InvalidOperation: (WebApiProxy.Tasks.Models.Configuration:TypeName) [], RuntimeException
       + FullyQualifiedErrorId : TypeNotFound
       + PSComputerName        : localhost
   
   Cannot find type [WebApiProxy.Tasks.Infrastructure.CSharpGenerator]: verify that the assembly containing this type is loaded.
       + CategoryInfo          : InvalidType: (:) [New-Object], PSArgumentException
       + FullyQualifiedErrorId : TypeNotFound,Microsoft.PowerShell.Commands.NewObjectCommand
       + PSComputerName        : localhost
   
   Generating proxy code...
   You cannot call a method on a null-valued expression.
       + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
       + FullyQualifiedErrorId : InvokeMethodOnNull
       + PSComputerName        : localhost
   
7. onionhammer

   reopened this on Mar 1, 2016
8. faniereynders commented on Mar 1, 2016

   

   faniereynders

   on Mar 1, 2016

   Member

   More actions

   What version of Powershell & VS are you using?
9. onionhammer commented on Mar 1, 2016

   

   onionhammer

   on Mar 1, 2016

   CollaboratorAuthor

   More actions

   Visual Studio 2015 on windows 8.1?
10. faniereynders commented on Mar 2, 2016

    

    faniereynders

    on Mar 2, 2016

    Member

    More actions

    Weird I cannot seem to reproduce this. Just tested it on your config as well and it works. I did however make changes to the package file to include the libs on the correct build configuration inside the project
11. DigitalDel commented on Sep 9, 2016

    

    DigitalDel

    on Sep 9, 2016

    More actions

    @onionhammer did you ever resolve this? I've now started getting this error as well despite it previously working fine?
12. DigitalDel commented on Sep 9, 2016

    

    DigitalDel

    on Sep 9, 2016

    Last edited by DigitalDel

    More actions

    Problem identified.

    This will occur if you have multiple projects in your VS Solution. I have 3 projects in my Solution:

    • API
    • Class Library
    • MVC Application

    The MVC app is the one on which i am trying to generate the proxy code however when i edited the WebApiProxyCSharp.psm1 file to print out the project path it is returning the path for my API project not the path of the MVC project the package is installed on and which has the references to WebApiProxy.Core and WebApiProxy.Tasks.

    Anyone any advice on how to fix? I did try adding references to WebApiProxy.Core and WebApiProxy.Tasks to the other projects in my solution and but WebApiProxyCSharp.psm1 uses the project path to identify the config and output paths which are obviously in the API project not the MVC project where the package is installed.

    The only solution i can think of at the moment is to install the package on the API project, generate the proxy code there and manually copy the generated file to the correct project but it doesn't make it particularly friendly to work with.
13. onionhammer

    added a commit that references this issue on May 30, 2017

    Revert "fixing RestCode#85 bug when generating using ps script"

    ...

    27c05a6