|
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.
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: 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.
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, |
|||||||||||||||||||||||||||||||||||||||||||||||||||||
If they are not in there, then it's a bug.
Were your 5.0 templates put into the 'projectTemplateBackup' folder?