Hi Anne,

I had to play with this a bit to understand what you meant as I didn't think it behaved any differently at first. But I see a couple of things now:

2011
You open the package, change the location and at this point lose the name of the project. So you have to copy paste, or retype the project name into the path presented and the folder is created with the project in it.

2015
You open the package, change the location and at this point lose the name of the project. But now you can't add the name into the end of the path, you have to click browse and then add the name of the project so that the new empty folder is created with this name.

So there is an additional step here. But next you come to do the second package and in 2011 the path is remembered and in 2015 it is not. So I would have to browse to the new location every time. Indeed this is a little irritating and is what you are referring to I think.

This latter problem is interesting because when 2015 first came out I tested this and I'm pretty sure the location you used for the Project was retained so it became available the next time, which is what you want. But now it seems to revert to the default Project location every time. There is good reason for this I think and I documented this in an article which you may find interesting (I also noted the behaviour you want which I'm sure applied at the time):

I'll pick this up with the development team and see whether there were some changes here I missed after the last update.

Regards

Paul

Hi Anne,

I had to play with this a bit to understand what you meant as I didn't think it behaved any differently at first. But I see a couple of things now:

2011
You open the package, change the location and at this point lose the name of the project. So you have to copy paste, or retype the project name into the path presented and the folder is created with the project in it.

2015
You open the package, change the location and at this point lose the name of the project. But now you can't add the name into the end of the path, you have to click browse and then add the name of the project so that the new empty folder is created with this name.

So there is an additional step here. But next you come to do the second package and in 2011 the path is remembered and in 2015 it is not. So I would have to browse to the new location every time. Indeed this is a little irritating and is what you are referring to I think.

This latter problem is interesting because when 2015 first came out I tested this and I'm pretty sure the location you used for the Project was retained so it became available the next time, which is what you want. But now it seems to revert to the default Project location every time. There is good reason for this I think and I documented this in an article which you may find interesting (I also noted the behaviour you want which I'm sure applied at the time):

I'll pick this up with the development team and see whether there were some changes here I missed after the last update.

Regards

Paul