SqlBuilder | SQL statement builder , allow you to write SQL | SQL Database library

Since you are a beginner, this is just a wild guess. You have written down the code and want to execute it synchronously, which simplified means the code should be executed in the same order as the source code lines are written.

The sqlBuilder function is async and you want it to be executed before moving on. So, you need to write await sqlBuilder(partialInterval, data);. You get an error saying that await is only allowed in async functions. Therefore you defined an anonymous inner async function and call it.
But this is the wrong way!
Now, the anonymous inner function is called but it is called async. Therefore you have not gained anything since the code in the while loop does not wait for this anonymous async function to finish before going on. You need to make the whole function with the while loop async or need to to rewrite the code to use the Promise of the sqlBuilder function.

Turns out I can do this:

In CLR/CLI c++ you should not use string which is ambiguous. it may be std::string which is a different type from .NET's string. in particular it hard to tell when you use: using namespace std;.

What you should do is to use String^ which is a reference to a .NET class.

so your code should be something like:

Use the @inject directive to inject an instance of it:

This is an issue with the maven com.itfsw/QueryBuilder plugin version of the query builder. I was using

libraryDependencies += "com.itfsw" % "QueryBuilder" % "1.0.2"

upgrading to

libraryDependencies += "com.itfsw" % "QueryBuilder" % "1.0.4"

solved the issue

I had installed the .NET Core 3.1.102 SDK separately. Uninstalling that and falling back to the version that comes with Visual Studio Build Tools 2019 fixed the problem.

Modify Join leftJoin(Sql Sql); to Join leftJoin(Sql Sql);, full source code:

There are multiple scenarios where that won't work. The good news is that you shouldn't be using two seperate SqlConnections in the first place. Just use the DbContext's SqlConnection for Dapper/ADO.NET. The DbContext will clean up the SqlConnection and you don't even need an additional using block.

So just something like:

the below import fixed it