The better option is to use CommandTimeout during your context setup like:
public class DbConnect: IConnnectDb
{
private dbentitient _context;
// inject this to a db entity from constructor.
//inside each method now use the follow before u actually run the query to db.
_context.Database.SetCommandTimeout(400);
}
Note: EF Core will only execute the query with less than 100 seconds time. If it's more than that it keeps retrying and you never get to see the result.
That's my experience as of now, so let me know if you are able to fix it
EF Core 1.0 does timeout even more fast than EF Core 2.0.
If you're using the DI container to manage the DbContext (i.e. you're adding the DbContext to the service collection), the command timeout can be specified in the options.
In EF Core 3 and above, you can now configure this via connection string. But you need to migrate from 'System.Data.SqlClient' to 'Microsoft.Data.SqlClient'.
Replace System.Data.SqlClient with Microsoft.Data.SqlClient version 2.1.0 or greater.
Then in your connection string simply append the command timeout like so: