Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
8 years ago
Solved

Swagger URL for PBI Report Server

I am trying to generate a client in C# from the Swagger resful API on Power BI Report Server. In Visual Studio 2017 there is a feature where you can generate a client proxy from the Solution explorer...
  • mgmeyer's avatar
    mgmeyer
    8 years ago

    If you just want the JSON file you can get it from SwaggerHub here:

     

    https://app.swaggerhub.com/apis/microsoft-rs/PBIRS/2.0

     

    In the top right you'll see an arrow pointing down, click that and you should see and option to download the JSON. I just noticed that there were some codegen customisations that we missed for PBIRS but added for SSRS which may be why your getting compilation errors, I just added them in I'll try it on my end to make sure it works. However if you still want to try the editor let me know if you see any issues.

     

    Matt M.

figuerres's avatar
figuerres
New Member
8 years ago

hey i guess the generated code has changed and there is one more problem with it.

i got the C# client coe and this one part does not compile and i amtrying to see what the right whay is to make it work.
in apiclient.cs at about line number 138  is a bit of code like this:

                request.AddFile(
                    param.Value.Name,
                    param.Value.Writer,
                    param.Value.FileName,
                    param.Value.ContentType
                    );

now the item param.Value.Writer  is of type  Action<T>  where T is a Stream

the parameter on AddFile (  ... ) wants an array of byte

so i need to get the stream and then the bytes if this was not an Action<T> id have no problem.

but I am not familiar with that.

 

any ideas on what should be done here ??

figuerres's avatar
figuerres
New Member
8 years ago

so i found that this is related to a new build of RestSharp, i had to go to an older version to make it build.

so i gess the swagger hub generated code and RestSharp are not playing well together....

  • StolzHerz's avatar
    StolzHerz
    Helper I
    8 years ago

    The choice of Microsoft to use a Rest Api / Swagger looks very trendy, but from the point of view of a Visual Studio developer, the good old SOAP Web Service was more stable and easy to use.

     

    In fact, no other development tool except Visual Studio could generate a web service client from a SOAP WSDL definition. All other dev tools were overwhelmed ... Microsoft had to react to this fact and take a "more open" path, so that developers can use other tools to use their web service interfaces too.

     

    Now thats the result: Swagger IO, oh my god... Totally out of control :-(