Stubs aren't generated unless service is instantiated in the same project about refit HOT 3 CLOSED

For me this also happened by just putting the ISomeApi into another file in the same project than the file which does RestService.For.

So i had a ISomeApi.cs containing the ISomeApi Interface but calling RestService.For<ISomeApi>() from Client.cs in the same Project did result in an empty RefitStubs.cs (besides the PreserveAttribute) with the same error as described.

To workaround that i put a

public static class SomeApi
{
    public static ISomeApi GetService(string address)
    {
        return RestService.For<ISomeApi>(address);
    }
}

in the same file which works but is not that nice.

from refit.

👍 for this one. In my current project we are using a factory that wraps the calls for RestService.For (and adds logging and other interesting things) which makes the current implementation fall flat for us (when upgrading from Refit 1.3 to 2.0.2). As a side note calling Refit.RestService.For (because of a namespace clash) does not seem to generate any stubs.

from refit.

This will be fixed by #67, which should be merged when @paulcbetts has had time to review it. 😸

If you are desperate, you could build your own InterfaceStubGenerator.exe from that PR, but ⚠️ it may still have some changes coming before it's nugetted.

In the meantime, a temporary workaround is just to have another class in the same project as the interfaces that calls RestService.For<IYourInterface>() for all of the interfaces.

from refit.