May-01-2019, 04:40 PM
Alright, let's backup and try to clear up some things which may have confused you.
IIS is a server. It would sit between your application and the end user. It doesn't matter if you use Flask or Django, they'll both communicate through fast cgi with IIS. Getting that bridge setup can be done through IIS' Web Platform installer: https://www.iis.net/downloads/microsoft/fastcgi-for-iis
There's also a python module which looks like helps with the config files (or maybe more, the module is published by Microsoft, so it isn't 3rd party, I just am not entirely sure what it does): https://pypi.org/project/wfastcgi/
Django and Flask serve the same purpose in your application. It doesn't make sense to use both at the same time. Your assessment that Django does more out of the box is correct, and along with that, it's much more difficult to customize if you don't like a particular aspect of it.
IIS is a server. It would sit between your application and the end user. It doesn't matter if you use Flask or Django, they'll both communicate through fast cgi with IIS. Getting that bridge setup can be done through IIS' Web Platform installer: https://www.iis.net/downloads/microsoft/fastcgi-for-iis
There's also a python module which looks like helps with the config files (or maybe more, the module is published by Microsoft, so it isn't 3rd party, I just am not entirely sure what it does): https://pypi.org/project/wfastcgi/
Django and Flask serve the same purpose in your application. It doesn't make sense to use both at the same time. Your assessment that Django does more out of the box is correct, and along with that, it's much more difficult to customize if you don't like a particular aspect of it.