exe.manifest file (this is the approach used by Office applications): To know the DPI-awareness of an executable (such as devenv.exe of Visual Studio) you can use these approaches: Given that your extension is hosted in an application (Visual Studio), you don’t have the chance of declaring anything about the DPI awareness of your extension, you are conditioned by the DPI-awareness of the Visual Studio version that is hosting your extension.
#.net visual studio extensions windows 8.1
![.net visual studio extensions .net visual studio extensions](https://d2908q01vomqb2.cloudfront.net/0716d9708d321ffb6a00818614779e779925365c/2019/03/28/04-new-project.png)
![.net visual studio extensions .net visual studio extensions](https://i0.wp.com/blog.mwpreston.net/wp-content/uploads/2018/09/c-sharp-in-visual-studio.png)
#.net visual studio extensions pro
This first thing that I noticed (very horrified) when I installed Visual Studio and my MZ-Tools extension in the new MacBook Pro 13″ Retina that I purchased last month was that at 100% scaling (96 Dpi) everything looked very tiny and at 150% (144 Dpi) or 200% (192 Dpi) scaling MZ-Tools looked horrible with very wrong layouts.