Installing FDT 5.5 Beta uses the location "/Users/[username]/Library/Application Support/FDT" for installing templates. It should be specific to the IDE, ie "/Users/jansensan/Library/Application Support/FDT 5.5", otherwise it breaks the templates for FDT 5. Actually, every install should own their own templates (what if I created my own?) and maybe ask to either merge, or copy the old ones into the new ones.

Description

Installing FDT 5.5 Beta uses the location "/Users/[username]/Library/Application Support/FDT" for installing templates. It should be specific to the IDE, ie "/Users/jansensan/Library/Application Support/FDT 5.5", otherwise it breaks the templates for FDT 5. Actually, every install should own their own templates (what if I created my own?) and maybe ask to either merge, or copy the old ones into the new ones.

Alan K (Deprecated) added a comment - 20/Apr/12 11:53 PM Your templates are in your 'projectTemplateBackup' folder.
If they are not in there, then it's a bug.
Were your 5.0 templates put into the 'projectTemplateBackup' folder?

They are backed up, but it still breaks FDT 5's template functionality, therefore it qualifies as a bug. A newer version of the IDE should be able to live in parallel with the old one without affecting it, especially a beta version.

Mat Janson Blanchet added a comment - 20/Apr/12 11:57 PM They are backed up, but it still breaks FDT 5's template functionality, therefore it qualifies as a bug. A newer version of the IDE should be able to live in parallel with the old one without affecting it, especially a beta version.

1. In my work environment we have many projects new and archived between our NY and India offices. Up until recently we would open projects created with FDT4 with FDT4 and newer projects with FDT5. The reason is because for some reason the SDKs and launch profiles would often display errors if the project is opened in a different FDT version than it was originally created in. So keeping legacy versions is important to us.

2. We have created a handful of FDT templates for Mobile, Desktop and Web that incorporate FDT, Robotlegs and our own custom frameworks. We distribute these to every developer in the company. It seems that the beta has merged the previous versions in:
C:\Users\Admin\AppData\Roaming\FDT\projectTemplates
It created a backup folder here:
C:\Users\Admin\AppData\Roaming\FDT\projectTemplateBackup\FDT 5.5.0
the backup only has Desktop, Mobile and Web. Our custom templates are gone all together. Of course we have backups but its not ideal to have to replace everything.

In order to get around this we destroy the C:\Users\Admin\AppData\Roaming\FDT\ folder and let FDT create it when the app opens. Then we add our custom templates back for the appropriate FDT version

I'm happy to get into it more if this will help improve this process.
Thanks

Patrick Mullady added a comment - 30/Apr/12 05:36 PM I have to agree with Mat. I'll give you a couple of reasons why:
1. In my work environment we have many projects new and archived between our NY and India offices. Up until recently we would open projects created with FDT4 with FDT4 and newer projects with FDT5. The reason is because for some reason the SDKs and launch profiles would often display errors if the project is opened in a different FDT version than it was originally created in. So keeping legacy versions is important to us.
2. We have created a handful of FDT templates for Mobile, Desktop and Web that incorporate FDT, Robotlegs and our own custom frameworks. We distribute these to every developer in the company. It seems that the beta has merged the previous versions in:
C:\Users\Admin\AppData\Roaming\FDT\projectTemplates
It created a backup folder here:
C:\Users\Admin\AppData\Roaming\FDT\projectTemplateBackup\FDT 5.5.0
the backup only has Desktop, Mobile and Web. Our custom templates are gone all together. Of course we have backups but its not ideal to have to replace everything.
In order to get around this we destroy the C:\Users\Admin\AppData\Roaming\FDT\ folder and let FDT create it when the app opens. Then we add our custom templates back for the appropriate FDT version
I'm happy to get into it more if this will help improve this process.
Thanks

Same problem here,
I took care to install FDT 5.5 Beta in a separate folder, and create a new Workspace so as not to mess things up...
I'd really prefer if the Beta didn't break my working environment templates.
So I also agree with Mat that this is a bug,

Julien Nicault added a comment - 09/May/12 11:03 PM Same problem here,
I took care to install FDT 5.5 Beta in a separate folder, and create a new Workspace so as not to mess things up...
I'd really prefer if the Beta didn't break my working environment templates.
So I also agree with Mat that this is a bug,