3,312
edits
Changes
Jump to navigation
Jump to search
Line 5:
Line 5: − + + + + + +
How to work with Solution Patches (view source)
Revision as of 15:41, 21 December 2021
, 15:41, 21 December 2021no edit summary
Here follows an example:
Here follows an example:
1. Make sure it is the same version of the solution in "your new DEV" as in Production. If not, adjust version in "your new DEV".
1. Make sure it is the same version of the solution in "your new DEV" as in Production. If not, adjust version in "your new DEV".
2. Make a Clone of the solution in "your new dev". Under the Solution -> Clone -> Clone a Patch.
2. Make a Clone of the solution in "your new dev". Under the Solution -> Clone -> Clone a Patch.
3. You will then get a new Solution and in that Solution you do the changes you want to do, which are meant to be the "fix for production".
3. You will then get a new Solution and in that Solution you do the changes you want to do, which are meant to be the "fix for production".
4. Import the Patch to Production.
4. Import the Patch to Production.
5. Make sure to do the same change in the "real DEV" environment. Either by doing it manually or by adding the components to an unmanaged solution in "your new DEV" and import to "real DEV".
5. Make sure to do the same change in the "real DEV" environment. Either by doing it manually or by adding the components to an unmanaged solution in "your new DEV" and import to "real DEV".
6. The next time a deployment of the whole solution is done from "real dev" to Production, all Patches will be merged and you will get one solution in Production.
6. The next time a deployment of the whole solution is done from "real dev" to Production, all Patches will be merged and you will get one solution in Production.