Fix 264 and refactor

[Mosch0512]

closes #264

[gemini-code-assist]

Summary of Changes

Hello @Mosch0512, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses issue #264 by performing a comprehensive refactoring and cleanup of the Main.vcxproj file. The changes primarily focus on standardizing build configurations, streamlining the management of include and library paths, and improving the overall maintainability and robustness of the project's build settings. This effort aims to ensure a more consistent and reliable build process across different environments and configurations.

Highlights

• Build Configuration Standardization: Standardized include and library paths across various build configurations, removing hardcoded paths and consolidating common settings.
• Intermediate Output Directory Cleanup: Updated the output directories for intermediate files like type libraries and browse information files to use standard Visual Studio variables, improving consistency.
• Refactored Linker Dependencies: Adjusted linker dependencies and library directories, specifically moving shlwapi.lib and netcore library paths to be applied only in Global Release configurations.
• Consolidated Compiler Settings: Refactored multiple individual <ClCompile Update> blocks for performance-critical files into a single, more concise entry, improving project file readability.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request significantly refactors the Main.vcxproj project file, leading to a much cleaner and more maintainable build configuration. Key improvements include the removal of hardcoded absolute paths for dependencies like Boost and DirectX SDK, the consolidation of duplicated compiler settings, and the consistent use of standard MSBuild properties like $(SolutionDir) and $(IntDir). These are excellent changes that will improve build portability and reduce configuration complexity.

I have one concern regarding the change in linking shlwapi.lib. It has been moved to be linked only in Release builds, which means it's no longer linked for Win32 Debug builds. This could potentially cause linker errors if any code in that configuration depends on it. Please see my specific comment for details.

[gemini-code-assist]

The shlwapi.lib dependency has been moved from this Win32 platform definition group to a Global Release configuration group. This means it will no longer be linked in Win32 Debug builds. Please confirm that no functions from shlwapi.dll are used in debug configurations for the Win32 platform, as this change could lead to linker errors.