[Seidleroni]

Here is a fairly comprehensive list of what I use in Visual Assist on a daily basis and would love to have as part of Clang IntelliSense:

1. Syntax Highlighting (colors listed are those spec’ed by Visual Assist, but presumably should be configurable):
   1. Gold for <span style=”text-decoration: underline;”>classes</span>, <span style=”text-decoration: underline;”>structs</span>, <span style=”text-decoration: underline;”>interfaces</span>, <span style=”text-decoration: underline;”>namespaces</span>, <span style=”text-decoration: underline;”>typedefs</span>
   2. DarkKhaki for <span style=”text-decoration: underline;”>variables</span>
   3. BD63C5 for <span style=”text-decoration: underline;”>Enums</span>, <span style=”text-decoration: underline;”>preprocessor macros</span>
   4. FF8000 for <span style=”text-decoration: underline;”>functions</span> and <span style=”text-decoration: underline;”>methods</span>
2. Quick Search global symbol cache “Find Symbol” (Alt+Shift+S in VA)
3. Open File in Solution (Alt+Shift+O)
4. Toggle between source + header (Alt+O)
5. Go to implementation (Alt+G)
6. List Methods in File (Alt+M)
7. Find References (Alt+Shift+F). Finds all references for that symbol, even when it is used in an inherited class.

I’ve resorted to using VisualGDB without Clang IntelliSense, and with Visual Assist enabled for navigation, plus Resharper for their amazing Static Analysis. I don’t mind the expense of having these three components, but the lack of interoperability with each other and Clang IntelliSense is a bit of a bother. Basically I had to disable Clang IntelliSense, and disable Resharper for live Code Analysis. I just use Resharper for Code Inspection which finds more than your Static Analysis, but that could likely be how it is configured through the GUI. Happy to discuss further.

• This reply was modified 6 years, 4 months ago by Seidleroni.

[Seidleroni]

Nevermind, you are right. Resharper syntax highlighting doesn’t work properly with Clang IntelliSense enabled.

[Seidleroni]

Downloading the latest version of Resharper, it looks like it now works with VisualGDB (look at release notes here). The reason I’m looking into Visual Assist and Resharper is for the ease of navigation and syntax highlighting.

[Seidleroni]

I have emailed back and forth with Visual Asist. They are aware of this issue; no idea if/when it will be fixed. Does Resharper work well with VisualGDB or does it have its own issues as well?

[Seidleroni]

Works great now, thanks.

[Seidleroni]

That resolved all of the warnings, thank you very much.

[Seidleroni]

I am using the latest STM32 BSP, which shows up as 4.7. It doesn’t show that there are new versions. It shows that I have these versions in the SDKVersions.txt (below) Do I need to be using the STM32F7Cube HAL in my project for this to work?

 

STM32Cube_FW_F0_V1.9.0
STM32Cube_FW_F1_V1.6.0
STM32Cube_FW_F2_V1.7.0
STM32Cube_FW_F3_V1.9.0
STM32Cube_FW_F4_V1.21.0
STM32Cube_FW_F7_V1.11.0
STM32Cube_FW_H7_V1.2.0
STM32Cube_FW_L0_V1.10.0
STM32Cube_FW_L1_V1.8.0
STM32Cube_FW_L4_V1.11.0
STM32F0xx_StdPeriph_Lib_V1.5.0
STM32F10x_StdPeriph_Lib_V3.5.0
STM32F2xx_StdPeriph_Lib_V1.1.0
STM32F30x_DSP_StdPeriph_Lib_V1.2.3
STM32F37x_DSP_StdPeriph_Lib_V1.0.0
STM32F4xx_DSP_StdPeriph_Lib_V1.8.0
STM32L1xx_StdPeriph_Lib_V1.3.1

[Seidleroni]

Uninstalling/Reinstalling VisualGDB did the trick. After doing so, I had to rebuild the MSBuild file but that was pretty painless.

[Seidleroni]

I was able to get the log by calling the installer with the /i* parameter. The log contents are below. Any idea what the issue could be?

=== Logging started: 10/12/2017 7:47:30 ===
Action 7:47:30: INSTALL.
Action start 7:47:30: INSTALL.
Action 7:47:30: FindRelatedProducts. Searching for related applications
Action start 7:47:30: FindRelatedProducts.
FindRelatedProducts: Found application: {72B37D99-EAF9-4D62-9CD9-915B07371007}
Action ended 7:47:30: FindRelatedProducts. Return value 1.
Action 7:47:30: PrepareDlg.
Action start 7:47:30: PrepareDlg.
Info 2898.For WixUI_Font_Normal textstyle, the system created a ‘Tahoma’ font, in 0 character set, of 13 pixels height.
Info 2898.For WixUI_Font_Bigger textstyle, the system created a ‘Tahoma’ font, in 0 character set, of 19 pixels height.
Action 7:47:30: PrepareDlg. Dialog created
Action ended 7:47:30: PrepareDlg. Return value 1.
Action 7:47:30: VSFindInstances.
Action start 7:47:30: VSFindInstances.
Action ended 7:47:30: VSFindInstances. Return value 1.
Action 7:47:30: AppSearch. Searching for installed applications
Action start 7:47:30: AppSearch.
AppSearch: Property: INTEGRATED_VS90, Signature: VS90VGDBRegistrySearch
AppSearch: Property: INTEGRATED_VS2010, Signature: VS2010VGDBRegistrySearch
AppSearch: Property: INTEGRATED_VS2012, Signature: VS2012VGDBRegistrySearch
AppSearch: Property: INTEGRATED_VS2013, Signature: VS2013VGDBRegistrySearch
AppSearch: Property: INTEGRATED_VS2015, Signature: VS2015VGDBRegistrySearch
AppSearch: Property: INTEGRATED_VS2017, Signature: VS2017VGDBRegistrySearch
AppSearch: Property: VS2017_DIRECTORY_ALTERNATE, Signature: VS2017DevEnvSearch_Fix
AppSearch: Property: USAGE_REPORTS_ENABLED_ON_LAUNCH, Signature: rsSEND_USAGE_REPORTS
AppSearch: Property: VS90_ROOT_FOLDER, Signature: SearchForVS90RootPath
AppSearch: Property: VS90DEVENV, Signature: VS90DevEnvSearch
AppSearch: Property: VS2010_ROOT_FOLDER, Signature: SearchForVS2010RootPath
AppSearch: Property: VS2010DEVENV, Signature: VS2010DevEnvSearch
AppSearch: Property: VS2012_ROOT_FOLDER, Signature: SearchForVS2012RootPath
AppSearch: Property: VS2012DEVENV, Signature: VS2012DevEnvSearch
AppSearch: Property: VS2013_ROOT_FOLDER, Signature: SearchForVS2013RootPath
AppSearch: Property: VS2013DEVENV, Signature: VS2013DevEnvSearch
AppSearch: Property: VS2015_ROOT_FOLDER, Signature: SearchForVS2015RootPath
AppSearch: Property: VS2015DEVENV, Signature: VS2015DevEnvSearch
AppSearch: Property: VS2017DEVENV, Signature: VS2017DevEnvSearch
AppSearch: Property: VS2017_IDE_DIR, Signature: VS2017EnvironmentDirectorySearch
Action ended 7:47:30: AppSearch. Return value 1.
Action 7:47:30: SetVS2017_ROOT_FOLDER.
Action start 7:47:30: SetVS2017_ROOT_FOLDER.
Action ended 7:47:30: SetVS2017_ROOT_FOLDER. Return value 1.
Action 7:47:30: LaunchConditions. Evaluating launch conditions
Action start 7:47:30: LaunchConditions.
Action ended 7:47:30: LaunchConditions. Return value 1.
Action 7:47:30: SetcaTouchExtensionsFile.
Action start 7:47:30: SetcaTouchExtensionsFile.
Action ended 7:47:30: SetcaTouchExtensionsFile. Return value 1.
Action 7:47:30: SetINSTALL_VS2015.
Action start 7:47:30: SetINSTALL_VS2015.
Action ended 7:47:30: SetINSTALL_VS2015. Return value 1.
Action 7:47:30: SetINSTALL_VS2017.
Action start 7:47:30: SetINSTALL_VS2017.
Action ended 7:47:30: SetINSTALL_VS2017. Return value 1.
Action 7:47:30: ValidateProductID.
Action start 7:47:30: ValidateProductID.
Action ended 7:47:30: ValidateProductID. Return value 1.
Action 7:47:30: CostInitialize. Computing space requirements
Action start 7:47:30: CostInitialize.
Action ended 7:47:30: CostInitialize. Return value 1.
Action 7:47:30: FileCost. Computing space requirements
Action start 7:47:30: FileCost.
Action ended 7:47:30: FileCost. Return value 1.
Action 7:47:30: CostFinalize. Computing space requirements
Action start 7:47:30: CostFinalize.
Action ended 7:47:31: CostFinalize. Return value 1.
Action 7:47:31: MigrateFeatureStates. Migrating feature states from related applications
Action start 7:47:31: MigrateFeatureStates.
Action ended 7:47:31: MigrateFeatureStates. Return value 1.
Action 7:47:31: WelcomeDlg.
Action start 7:47:31: WelcomeDlg.
Action 7:47:31: WelcomeDlg. Dialog created
Info 2898.For WixUI_Font_Title textstyle, the system created a ‘Tahoma’ font, in 0 character set, of 14 pixels height.
Action 7:47:31: LicenseAgreementDlg. Dialog created
Info 2898.For WixUI_Font_Normal_Bold textstyle, the system created a ‘Tahoma’ font, in 0 character set, of 13 pixels height.
Action 7:47:33: SetupTypeDlgEx. Dialog created
Action 7:47:36: CustomizeDlg. Dialog created
Action 7:47:41: VisualStudioSelectDlg. Dialog created
Action 7:47:43: VerifyReadyDlg. Dialog created
Action ended 7:47:44: WelcomeDlg. Return value 1.
Action 7:47:44: ProgressDlg.
Action start 7:47:44: ProgressDlg.
Action 7:47:44: ProgressDlg. Dialog created
Action ended 7:47:44: ProgressDlg. Return value 1.
Action 7:47:44: ExecuteAction.
Action start 7:47:44: ExecuteAction.
Action 7:47:45: INSTALL.
Action start 7:47:45: INSTALL.
Action 7:47:45: FindRelatedProducts. Searching for related applications
Action start 7:47:45: FindRelatedProducts.
Action ended 7:47:45: FindRelatedProducts. Return value 0.
Action 7:47:45: VSFindInstances.
Action start 7:47:45: VSFindInstances.
Action ended 7:47:45: VSFindInstances. Return value 0.
Action 7:47:45: AppSearch. Searching for installed applications
Action start 7:47:45: AppSearch.
Action ended 7:47:45: AppSearch. Return value 0.
Action 7:47:45: SetVS2017_ROOT_FOLDER.
Action start 7:47:45: SetVS2017_ROOT_FOLDER.
Action ended 7:47:45: SetVS2017_ROOT_FOLDER. Return value 1.
Action 7:47:45: LaunchConditions. Evaluating launch conditions
Action start 7:47:45: LaunchConditions.
Action ended 7:47:45: LaunchConditions. Return value 1.
Action 7:47:45: SetcaTouchExtensionsFile.
Action start 7:47:45: SetcaTouchExtensionsFile.
Action ended 7:47:45: SetcaTouchExtensionsFile. Return value 1.
Action 7:47:45: SetINSTALL_VS2015.
Action start 7:47:45: SetINSTALL_VS2015.
Action ended 7:47:45: SetINSTALL_VS2015. Return value 1.
Action 7:47:45: SetINSTALL_VS2017.
Action start 7:47:45: SetINSTALL_VS2017.
Action ended 7:47:45: SetINSTALL_VS2017. Return value 1.
Action 7:47:45: ValidateProductID.
Action start 7:47:45: ValidateProductID.
Action ended 7:47:45: ValidateProductID. Return value 1.
Action 7:47:45: CostInitialize. Computing space requirements
Action start 7:47:45: CostInitialize.
Action ended 7:47:45: CostInitialize. Return value 1.
Action 7:47:45: FileCost. Computing space requirements
Action start 7:47:45: FileCost.
Action ended 7:47:45: FileCost. Return value 1.
Action 7:47:45: CostFinalize. Computing space requirements
Action start 7:47:45: CostFinalize.
Action ended 7:47:45: CostFinalize. Return value 1.
Action 7:47:45: MigrateFeatureStates. Migrating feature states from related applications
Action start 7:47:45: MigrateFeatureStates.
Action ended 7:47:45: MigrateFeatureStates. Return value 0.
Action 7:47:45: InstallValidate. Validating install
Action start 7:47:45: InstallValidate.
Action ended 7:47:45: InstallValidate. Return value 1.
Action 7:47:45: RemoveExistingProducts. Removing applications
Action start 7:47:45: RemoveExistingProducts.
RemoveExistingProducts: Application: {72B37D99-EAF9-4D62-9CD9-915B07371007}, Command line: UPGRADINGPRODUCTCODE={020C3694-E978-46E8-870F-83549561CE67} CLIENTUILEVEL=0 REMOVE=ALL
Action 7:47:45: INSTALL.
Action start 7:47:45: INSTALL.
Action 7:47:45: FindRelatedProducts. Searching for related applications
Action start 7:47:45: FindRelatedProducts.
Action ended 7:47:45: FindRelatedProducts. Return value 0.
Action 7:47:45: VSFindInstances.
Action start 7:47:45: VSFindInstances.

[Seidleroni]

Great, thank you.

[Seidleroni]

I can’t use a Linux VM for that because it is an embedded project (STM32).

[Seidleroni]

That would be wonderful. I look forward to it the feature in Preview 3.

[Seidleroni]

BTW, we are currently experimenting with storing $(BSP_ROOT) paths in the .vcxproj files instead of the relative paths to relocated BSPs and are planning to include this in the upcoming Preview 3 of v5.3. This should solve the problem you mentioned.

Regarding this statement, would that mean that I could put the BSPs in a C:\ directory and that would be an absolute path instead of relative path?

[Seidleroni]

The issue with relocating the BSP as shown in the example is that the BSP directory is still relative to the project directory. That only makes sense if you want to include the entire BSP in source control, but the STM32 BSP alone is > 600 MB. Wouldn’t it make sense to just install all of the BSP’s and Toolchain in the VisualGDB program files directory instead? This way, every user could just open the project and compile, provided they have all the proper BSPs/toolchains installed. No environment variables would need to be configured or anything. As far as I can tell, this is how most embedded compilers operate and would allow any user on a computer (or multiple computers) to work easily with no configuration necessary.

[Seidleroni]

Will this feature be available as part of 5.3? I really love VisualGDB, but not having this feature work makes it difficult to work with multiple developers as well as using a build server.

[Author]

Posts