When is it appropriate to delete an instance vs resetting it?
From my understanding, deleting an instance removes it completely. Resetting it does the same thing as delete except "reprovisions" it.
What is meant by "reprovisioning" it?
Delete - removes the entire organization from your tenant, you lost it & don’t need again
Reset - just removes your customizations (if any made), like Form UI changes, navigation menu or ribbon changes, JavaScript, workflows or plugins will be washed out. The org will go to its original OOB vanilla state to start over
Provisioning or Reprovisioning is nothing but spinning the SaaS with its factory settings :)
Related
Pretty much; i open a new premade project in Unreal, i modify simple things, such as : place new objects, create simple blueprint in Level Blueprint (so it affects the level) and then save and close.
Problem is, next time i open that project, EVERYTHING is reset to default, like i haven't touched anything and I'm forced to redo everything, thing that is annoying when you followed a course.
Any help on how to actually save my changes? This is severely impacting my studies.
I tried to save the project and set the map i used as default map when opening the project.
I tried to save layout (might not be useful at all, but I'm still green in Unreal)
Tried to save the blueprint of the level but still nothing, even compiling doesn't seem do do anything to lock it and save it.
Thanks for your help in advance.
I was wondering if it was possible to branch by collection in TFS2010?
Basically, I have a collection called "ReleaseTesting", and when I right click on it I am able to see the menu for "Branching and Merging", however it is greyed out.
So, is it possible to branch by collection? Just by the fact that the menu is there, leads me to believe that this is true.
If you mean branch from one collection to another then no it's not possible (or branch from the root of a collection to create another). Behind the scenes collections in TFS are seperate databases and cannot share any artefacts (code, work items, builds etc).
If you need to move code between collections and maintain history the you could use the TFS integration platform
Hmm, I think you are on the right track. Remember that TFS has it's own permissions. So if something is greyed out, it could be because you don't have permissions.
For example, the new folder icon for me is greyed out sometimes, depending where in the folder tree I am.
Standard answer- contact you administration, i know that is not very helpful though.
Sometimes accidentally you move some files from somewhere to anywhere ? on Solution Explorer.
Is there any way for asking on drag & drop operations?
Or disabling drag&drop completely .
If you user tfs it may cause other annoying problems.
A Scenario Hard to Achieve but I Succeed!)
Suppose you don't know these moved files.
On Compile you delete these files(mostly they cause errors),if you check-in then after delete ,say goodbye to your files gone and on tfs you can't add a new file it's name used previously .
You need to get a previous version and so on...
If I'm working on lots of things at a time I would like to group the files that I've changed into 'change lists' similar to TortoiseSVN change list feature. Is there a way to do this in TFS?
Is there a way to do this in TFS?
Not in the way linked to (as far sa I can tell).
You can use "Shelvesets" to save ongoing changes (and, optionally, remove them as pending changes in your workspace) which allows saving your state when switching to work on something else.
I'm using AnkhSVN with Visual Studio 2010.
When I start to edit a file, I'd like to either automatically update the file from the repository, or be warned that it needs updating.
Is this possible?
Would keeping the working copy updated be of use?
If so, you can use this:
How do I automatically update a Subversion working copy?
There's not really a way to do this in Subversion, except when you're using locking and svn:needs-lock on files. The reason is that when you start editing your file can be up to date, but when you want to commit it's changed, and needs updating. Subversion will check for this case and notify you to update when you try to commit.
To get notification of files others are working on, you can go to the "Recent changes" tab in the Pending Changes window (View -> Pending Changes, then click the 3rd tab from the top). You can configure this to update every 'X' time, UI should be pretty self explanatory here.
See my answer here for info on svn:needs-lock, but make sure you understand the pitfalls of exclusive locking of files.