# \[native\] need help with Visual Studio plugin **URL:** \ **Category:** Help/Discuss\ **Created:** [September 11, 2015, 7:27pm UTC](https://discuss.gradle.org/t/native-need-help-with-visual-studio-plugin/11604 "2015-09-11T19:27:42Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![RalfSchallenberg](https://avatars.discourse-cdn.com/v4/letter/r/e47774/32.png) [@RalfSchallenberg](https://discuss.gradle.org/u/RalfSchallenberg)\ **Post date:** [September 11, 2015, 7:27pm UTC](https://discuss.gradle.org/t/native-need-help-with-visual-studio-plugin/11604/1 "2015-09-11T19:27:42Z")
Hi, I have a couple of issues with the generation of Visual Studio solution and project files: 1. Is it possible to configure custom _filters_ (virtual folders in the solution) for projects and files? I would like to group related projects into filters and do the same for files inside projects to tidy up everything. The flat default layout can be a little inconvenient for bigger solutions. 2. I noticed that the generated projects are missing include paths for standard libraries and the Windows headers. This doesn’t affect the build, because that is still done by Gradle, but it does affect the IntelliSense system in the editor. Because IntelliSense can’t find the standard headers, it reports them as unknown and doesn’t provide any form of auto-completion. That’s inconvenient too. Is there a remedy? 3. In Visual Studio there are _solution configurations_ (for build types like _debug_ and _release_) and _solution platforms_ (like _Win32_ or _x64_). The Visual Studio plugin doesn’t care for the platform at all. It just generates different configurations for all possible combinations of build type and platform. Again this doesn’t affect the build, but confuses IntelliSense, because when I select a 64-Bit configuration like _x64Debug_, the platform in Visual Studio is still _Win32_. The effect is that IntelliSense thinks compiler macros that are predefined for 64-Bit builds (like `_WIN64`, `_M_X64` or `_M_AMD64`) are undefined.