project refrence vs global tool package

[Freysi21]

First of, I love this product. Second I have created a thing called shotgun https://github.com/[Freysi21/Shotgun](https://github.com/Freysi21/Shotgun) which tries to accomplish the same thing as dab but only the rest part with abstract classes. I use this package for all data retrival apis within my workplace (which requires on prem infrastructure) and have created a bunch of stuff for dotnet webapis to plug into logging and etc.

I wanna scrap my project and use dab but I don't see a way for me to do so whilst not being able to plug into the on prem infrastructure which i do via middlewares and etc. I could use YARP in front of a dab api but that feels more like a hack. Is there a plan to be able to use dab as a nuget package within a dotnet project rather then as a global tool ?

[aaronburtle]

Hi @Freysi21 thanks for the question, wanted to let you know that I am following up on this and will have an answer for you shortly.

[aaronburtle]

thanks mate

Hi @Freysi21 after following up with some more folks on the team, this is something that we would like to add to DAB at some point in the future, but it won't be coming anytime soon. Using YARP as you suggested might be the best workaround in the meantime, or it could be possible to run DAB as its own processes and then interact with it through HTTP.

Thanks for the question!

[Freysi21]

Keep me posted, I'm happy to help with this feature.

[Freysi21]

Just to clarify "running DAB as its own process". Would my dotnet WebAPI controller endpoint implementation look something like this ?
assuming i run dab start in a dockerfile or some for my container running the webapi ?

        [HttpGet("data")]
        public async Task<IActionResult> GetData()
        {
            var response = await _httpClient.GetAsync("http://localhost:5000/api/data");
            if (response.IsSuccessStatusCode)
            {
                var data = await response.Content.ReadAsStringAsync();
                return Ok(data);
            }
            return StatusCode((int)response.StatusCode, response.ReasonPhrase);
        }

[aaronburtle]

Keep me posted, I'm happy to help with this feature.

We are happy to accept external contributions, and if you are able to pick up this work it will most definitely speed up the timeline. This is something that we would love to add but as of right now it has no ETA on our end.

Just to clarify "running DAB as its own process". Would my dotnet WebAPI controller endpoint implementation look something like this ? assuming i run dab start in a dockerfile or some for my container running the webapi ?

        [HttpGet("data")]
        public async Task<IActionResult> GetData()
        {
            var response = await _httpClient.GetAsync("http://localhost:5000/api/data");
            if (response.IsSuccessStatusCode)
            {
                var data = await response.Content.ReadAsStringAsync();
                return Ok(data);
            }
            return StatusCode((int)response.StatusCode, response.ReasonPhrase);
        }

Yes, exactly, you would start DAB as its own process (eg: dab start --config my-config.json), then your .NET application acts as a proxy, forwarding requests to DAB over HTTP and then returning the response to the caller.

As you mentioned another option is to use YARP where all API requests could be proxied to DAB and your controller wouldn't have to handle these requests manually.

[Freysi21]

For an external contribution. Would you accept an implementation that included YARP as a dependency?