adhocTemplates relative vs absolute path in project file

Posts   
 
    
rbrown
User
Posts: 36
Joined: 11-Jun-2008
# Posted on: 06-Sep-2024 20:58:15   

We are using an adhocTemplates file, which is located within our source repo (as opposed to the My Documents area). It's working fine, but the designer seems to embed the absolute path into the project file. This causes issues when two developers don't have the same working path and so on. Is there a way to preserve the relative path?

I have configured the "Additional tasks folder" and "Additional templates folder" to this folder using relative paths. The designer finds it, but ultimately it still embeds the full path into the project file each time.

E.g. git shows this diff when two different devs have generated:

        <AdhocTemplateSets>
-          <AdhocTemplateSet Name="C:\Users\bob\source\repos\Product\Source\DAL\.\llblgen\LLBLGen Pro v5\Tasks\Product.adhoctemplates" />
+          <AdhocTemplateSet Name="C:\Dev\Product\Source\DAL\.\llblgen\LLBLGen Pro v5\Tasks\Product.adhoctemplates" />
        </AdhocTemplateSets>
Otis avatar
Otis
LLBLGen Pro Team
Posts: 39738
Joined: 17-Aug-2003
# Posted on: 07-Sep-2024 09:34:11   

This is currently not supported, it saves the full path in the project file. We acknowledge this isn't ideal tho, we'll see if we can fix this in a future version. The main issue is that the code loading the adhoc template sets gets the set of files to load the contents of after a filter has obtained all loadable files from various sources. So it's unclear at that point what to strip off to get the relative filename.

Additionally, perhaps some people want this to be an absolute path so we have to add a setting for this.

Frans Bouma | Lead developer LLBLGen Pro