Unknown said:

So I have to manually re-create all project templates?

That would be my advice.

Unknown said:

Creating a project with the old ones and saving that as project template at the end of the new project wizard will not do the job.

I'm pretty sure that this is what you are exposing yourself to:

1. create a project in 2021 with templates from 2019
   
   
2. you now have a project that is potentially based on the following:
   - older versions of the filetypes
   - missing features
   - underlying logic used in the software that is looking for something only available in a new template
   
   
3. when you create a new template from the settings in that project you will be continuing to replicate the old settings

For some projects you may be just fine and might not even realise the difference until you come across a bug that was resolved in the new version, or a setting that you think should be available to you but it's not.

Unknown said:

Can I export settings (file types, regex, validation settings etc.) and re-import them into the new project template?

This all depends, but on the whole I would say this is all possible.  If you do come across a problem with this approach then please report them.  Missing filetypes from one version to other would be a case where this probably won't work for example.

This is my experience with this, and we do quite often see problems that are caused as a result of users doing just this.  So my recommendation would be to always recreate the templates.  I would also import settings as you suggest, but I would not attempt to reuse templates from older versions in the new ones.

Hi

Is this still true today or has anything changed in the meantime, now that we are on Studio 2021?
Many LSPs have a lot of project templates and recreating them all manually every time a new version of Studio comes out is a big and tedious task.

Is there really no way to automate this process?

What about opening the existing template in the new version of Studio and (1) adding missing and new filetypes (link on top) and (2) resetting the settings. This would reset the personalized filetype settings to default values but at least use the new version of the filetypes.
What else apart from the filetype settings could be incompatible in the new project template?

Any idea on how to ease this migration task in the future is welcome.

Walter

Walter Blaser

Walter Blaser said:

Is there really no way to automate this process?

To do this properly and avoid problems then no.  It's something that should be addressed by development to upgrade project templates as part of a routine in Studio.

Walter Blaser said:

What about opening the existing template in the new version of Studio and (1) adding missing and new filetypes (link on top) and (2) resetting the settings. This would reset the personalized filetype settings to default values but at least use the new version of the filetypes.

Sure... you can do this.

Walter Blaser said:

What else apart from the filetype settings could be incompatible in the new project template?

Just take a look in the Project Settings and then think about every bug that gets fixed, or enhancement, that could result in something different in here.  It may be that your suggestion would be just fine and I'm pretty sure many users do this.  But sometimes something they do caches up with them and a recreation of the template is the only resolution.

So until we have a proper process for upgrading project templates automatically and correctly I will always recommend recreation.

Thanks Paul.

So we still hope someone will adress this issue and come up with an automated solution.