- Create EV in solution on the DEV environment
- Set "Current Value" to a value appropriate for the DEV environment
- Before EACH (!!!) deployment, REMOVE the value of each EV. (I forgot this today and now I'm in trouble, see below...)
- After deleting the values, deploy the solution to the managed target environment
- During deployment, you'll be asked to specify the value (appropriate to the target environment)
- Complete deployment afterwards
- Go to 2. (Set "Current Value"...) and continue with the next development iteration
I'm stuck! It seems having forgot to remove the values killed my chances of re-deploying the solution. Luckily, the target environment is only a TEST environment and scrapping the whole solution will not be a disaster - but soon we will deploy to a production environment and I'm almost certain, that one day I will forget to remove the EV variables again during a rushed deployment and may become stuck again. Scrapping the whole solution won't be possible then. There HAS to be an easier and less dangerous way of using EVs in managed solutions!
A blog post suggested that EVs shouldn't be part of a managed solution at all, instead the should be in their own unmanaged solution and deployed separately to the target environment. I'll experiment with the idea for sure, but I'm also a little doubtful it will work...
Is there a rock-solid Best Practice for this?