I was wondering how you can control the folder structure which is generated from the vstemplate files. I originally thought that this is maybe somehow controlled by "CreateNewFolder" but changing that to false had no effect. No matter what i do it seems like i always get a folder structure like
solution/wizardname/wizardname.projectA
solution/wizardname/wizardname.projectB
instead of
solution/wizardname.projectA
solution/wizardname.projectB
https://docs.microsoft.com/en-us/visualstudio/ide/template-parameters?view=vs-2019 did not seem to point out any ways of doing this.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@taori -- Andreas, you may find these links helpful in finding answers:
@WilliamAntonRohm Not really no. All 3 of them involve digging through hundreds of unrelated articles.
Personally i was so bothered with the tedious process that i wrote https://github.com/taori/Amusoft.VisualStudio.TemplateGenerator so i never have to deal with managing multi project templates again. Hence my request to get some information on this in order to generate the templates in a fashion where i can generate the templates into a flat folder hierarchy instead of a nested one :)
@WilliamAntonRohm This is so ridiculous. I've spent hours trying to solve the multi-project template structure, namely the now infamous "weird additional folder". No way of dealing with it if not through some kind of Wizard-ry magic.
There is literally not a single clear, reliable source in MDSN that tackles this common problem. It can't be that hard to solve it.
That "weird additional" made me result into writing this: https://github.com/taori/Amusoft.VisualStudio.Extensions/tree/master/src/Tooling so i can move folders to a new destination while altering the solution references.
Took me dozens of hours to develop it and moving it manually is probably faster... but hey... it was more fun than being annoyed by the folder structure? :laughing:
this really needs fixing though. Noone should go through this just to have a clean folder structure
That "weird additional" made me result into writing this: https://github.com/taori/Amusoft.VisualStudio.Extensions/tree/master/src/Tooling so i can move folders to a new destination while altering the solution references.
That sounds great @taori -- any chance you could provide a bit of documentation on how to use the extension?
I'm bothered by this issue too. Project templates have so much potential, but they really need some work. I'll check out your project, taori.
That "weird additional" made me result into writing this: https://github.com/taori/Amusoft.VisualStudio.Extensions/tree/master/src/Tooling so i can move folders to a new destination while altering the solution references.
Took me dozens of hours to develop it and moving it manually is probably faster... but hey... it was more fun than being annoyed by the folder structure? 😆
this really needs fixing though. Noone should go through this just to have a clean folder structure
Thank you for sharing this.
I, too, have spent countless hours attempting to get around this "weird" folder structure. I believe this is just another example of Microsoft providing a really great tool that stops short of providing a complete solution to their end users. It's a shame we need to resort to writing custom tools to provide the consistency (inherent folder structure when creating new Solutions in VS) that should have been a forethought in the minds of the team who developed this tool.
That "weird additional" made me result into writing this: https://github.com/taori/Amusoft.VisualStudio.Extensions/tree/master/src/Tooling so i can move folders to a new destination while altering the solution references.
Took me dozens of hours to develop it and moving it manually is probably faster... but hey... it was more fun than being annoyed by the folder structure? 😆
this really needs fixing though. Noone should go through this just to have a clean folder structureThank you for sharing this.
I, too, have spent countless hours attempting to get around this "weird" folder structure. I believe this is just another example of Microsoft providing a really great tool that stops short of providing a complete solution to their end users. It's a shame we need to resort to writing custom tools to provide the consistency (inherent folder structure when creating new Solutions in VS) that should have been a forethought in the minds of the team who developed this tool.
Running into this issue as well. It real sad that Microsoft can't fix what should be a simple issue for them. Going to try that tool and see if it is going to end up being the last step in our new solution making process because MS can't do their job.
I would not expect them to invest a lot of time anymore on this. There is a new templating system now after all.
have a look at this