Application Repository Vs. Publish to Update Set

[Marskh11]

We use custom scoped applications quite often and notice if we use application repository to publish an app from one instance to another, it only displays in studio on that sub-prod instance. 

However if we use publish to an update set, we can find the application in studio on that instance. 

Does that sound accurate? If we want to see our applications in studio we have to publih to an update set and can't use the repository? 

[Allen Andreas · Accepted solution]

Hello,

The custom application on other instances shouldn't need to be accessed within Studio as that is a development tool. The app isn't supposed to be under development once it's been published to the instance repo and subsequently installed on other instances.

If you needed to access it via Studio for whatever reason, that should be done in Dev.

The point being that the application is the same across all instances when using the instance app repo.

It's "available" in Studio (in other instances) when publishing to an update set and further committing that to another instance, because it's not "published" in the traditional sense (app repo) and is available for development instead...because again, it's not "published".

Publishing to an update set basically just means you're capturing the entire app in an update set. It doesn't mean it's "published" in the same definition as a custom app that's published to the instance app repo.

Please mark reply as Helpful/Correct, if applicable. Thanks!

[Marskh11]

That makes perfect sense. Thanks so much.