Unknown said:

I am about to install Studio 2015, and I am wondering if it is possible to choose another location of the "Studio 2015" folder than in the "Documents" folder?

Quite simply, yes you can.  Don't get into moving your documents folder... actually I don't think you suggested this in the first place.  Just decide where you want your folders to be and start using that location.  You can even set the preferred location in your project templates:

You can do this at anytime.

Regards

Paul

Unknown said:

Jerzy said that a few files must stay there. But you disagree?

I don't disagree.  This folder will be created and will always be there:

c:\Users\[USERNAME]\Documents\Studio 2015\Projects\

But this doesn't mean you have to put your projects in there if you don't want to.  I'd recommend you do because Studio works better when you let it do what it wants to, but using a different location or even multiple locations for your projects is not too hard to manage in Studio 2015.

The projects.xml file will however always be in the Studio default folder here:

c:\Users\[USERNAME]\Documents\Studio 2015\Projects\

That's what Jerzy means.

Unknown said:

What is the problem with moving my Documents folder?

No problem if you like to make work for yourself for no particularly good reason!  See the link from Jerzy.

Paul

No problem if you like to make work for yourself for no particularly good reason!

Hi Marie,

Unknown said:

Do you think normal updates are likely to cause any problems?

You might never have any problems so I can't really say... but I'd just avoid it because too many applications use this stuff by default and Windows almost forces that policy as much as it can.

Unknown said:

Are the files which must remain in the Documents\Studio 2015 folder important in the sense that I should back them up regularly, or can I just back up my TMs and projects and forget about the files in the Documents\Studio 2015 folder?

I think it's your resources and working files that are the most important.  So I'd back up the projects, the TMs the Termbases, the AutoSuggest Dictionaries... basically anything that I had to spend time creating.  The rest you can easily put back as they are just metadata telling Studio where to find them.  If I had hundreds of open projects because I worked as a Project Manager for a large LSP for example then I might consider trying to do something with the projects.xml, but otherwise I'd just reopen the projects I wanted if necessary.

There are also more resources in the user folders that Studio doesn't share very well, such as AutoCorrect lists and also resources your can export import like QA settings.  So getting everything is a real chore and we have tried to get some interest through the AppStore community in extending a tool to help manage all of this.  But sadly it's still languishing as a good idea that never took off :-(

Would be better if Studio itself just had an archive facility or backup facility that allowed an easy backup and restore of everything!  Interestingly after two months of giving people the opportunity to ask for an idea to be built that they liked this one never came up (other than a couple of people asking for a project archiving tool), so maybe it's not really anything people worry that much about anyway... at least not until they need to move computers!!

Regards

Paul

Hi Marie,

Unknown said:

Do you think normal updates are likely to cause any problems?

You might never have any problems so I can't really say... but I'd just avoid it because too many applications use this stuff by default and Windows almost forces that policy as much as it can.

Unknown said:

Are the files which must remain in the Documents\Studio 2015 folder important in the sense that I should back them up regularly, or can I just back up my TMs and projects and forget about the files in the Documents\Studio 2015 folder?

I think it's your resources and working files that are the most important.  So I'd back up the projects, the TMs the Termbases, the AutoSuggest Dictionaries... basically anything that I had to spend time creating.  The rest you can easily put back as they are just metadata telling Studio where to find them.  If I had hundreds of open projects because I worked as a Project Manager for a large LSP for example then I might consider trying to do something with the projects.xml, but otherwise I'd just reopen the projects I wanted if necessary.

There are also more resources in the user folders that Studio doesn't share very well, such as AutoCorrect lists and also resources your can export import like QA settings.  So getting everything is a real chore and we have tried to get some interest through the AppStore community in extending a tool to help manage all of this.  But sadly it's still languishing as a good idea that never took off :-(

Would be better if Studio itself just had an archive facility or backup facility that allowed an easy backup and restore of everything!  Interestingly after two months of giving people the opportunity to ask for an idea to be built that they liked this one never came up (other than a couple of people asking for a project archiving tool), so maybe it's not really anything people worry that much about anyway... at least not until they need to move computers!!

Regards

Paul