Sysprogs forums › Forums › VisualGDB › Bug : Import folder recursively has been broken for ages
- This topic has 4 replies, 2 voices, and was last updated 2 years, 8 months ago by Rob Belcham.
-
AuthorPosts
-
February 8, 2022 at 03:38 #32160Rob BelchamParticipant
Can I please request that fixing the recursive folder import be added to the TODO list ? It has been broken for some time now.
You used to be able to right click an existing folder (filter) in the solution explorer and select Add -> Import Folder Recursively and the selected files / folders would then appear underneath the folder you originally clicked. This doesn’t happen any more and all the files / folders get added to the root level of the solution so you have to go through manually moving them all.
Thanks
February 8, 2022 at 07:46 #32161supportKeymasterUnfortunately, it is hard to suggest anything specific based on the description you provided.
In order for us to provide any help with this, we need to be able to reproduce the problem on our side.
Please provide complete and detailed steps to reproduce the issue as described below:- The steps should begin with launching Visual Studio. They should include every step necessary to create the project from scratch and reproduce the issue.
- Please make sure the steps do not involve any 3rd-party code as we will not be able to review it. If the problem only happens with a specific project, please make sure you can reproduce it on a clean project created from scratch.
- The steps should include uncropped screenshots of all wizard pages, VisualGDB Project Properties pages and any other GUI involved in reproducing the problem. This is critical for us to be able to reproduce the problem on our side.
You can read more about the best way to report VisualGDB issues in our problem reporting guidelines, If you do not wish to document the repro steps and save the screenshots, please consider recording a screen video instead and sending us a link to it.
Please note that many VisualGDB issues are caused by selecting an incompatible combination of settings at some point. We are generally not able to review specific projects and find the specific settings that were set incorrectly. We recommend checking the projects into source control and keeping a track of all changed settings to avoid breaking the projects.
You can also try checking various diagnostic output from various parts of VisualGDB as described on this page. Although we won’t be able to review it for a specific project unless the we can reproduce the problem from scratch, checking it might provide some clues on what is causing the unexpected behavior.
February 14, 2022 at 03:01 #32192Rob BelchamParticipantApologies for the terrible bug report! Here’s a clearer description of the issue.
- Open VS
- Create a new VGDB project with Custom Project Wizard
- Click Next / Finish to create an empty project
- Delete the empty
Header files
andSource files
folders - Create an empty folder in File Explorer and call it
Project
- Inside the
Project
folder, create a folder calledA
- Inside the
A
folder, create a couple of empty files egA1.h
andA2.h
- Inside the
A
folder still, create a folder calledB
- Inside the
B
folder, create a couple of files e.gB1.h
andB2.h
- Right click the project and click Add -> import folder recursively
- Leaving “the folder is located on this computer” selected, browse to the
Project
folder created above and select it - Enable
Bypass "Source Files" and "Header Files" folders
- Click OK
- File tree is successfully imported as expected. (see Screenshot 1)
- Inside the
A
folder in Windows File explorer, now create aC
folder withc1.h
andc2.h
inside it. - Right click the
A
folder in the VS solution explorer and repeat steps 10,11&12 but selecting the C folder created in 15. (Screenshot 2) - At this point, I would expect the C folder to be created underneath the A folder in the project window but it doesn’t, it puts the c1.h files at the root of the project (screenshot 3)
- What I would expect is to see screenshot 4. I think part of the issue is that the folder you select does not get created, only it’s contents, and it doesn’t place the contents at the level you selected in the tree.
- The use case for this is working with a large project, where someone adds a new submodule, or folder and you want to import it into the project in a single step.
Attachments:
You must be logged in to view attached files.February 16, 2022 at 20:38 #32233supportKeymasterThanks for the detailed repro steps. The issue was triggered by adding folders to first-level Solution Explorer nodes with source/header filters disabled. As it is a relatively rare scenario, it makes sense why it wasn’t caught by our tests or reported by anyone else.
We have fixed the issue in the following build (and also added a checkbox for creating an extra node for the imported folder itself): VisualGDB-5.6.104.4538.msi
February 21, 2022 at 08:36 #32282Rob BelchamParticipantAmazing, thankyou! Works perfectly 🙂
-
AuthorPosts
- You must be logged in to reply to this topic.