Hello everyone, long time no see. Writing this to communicate that I just finished the merge of v5.1 code into the community fork of Company Communicator.
So please pay attention: If you are using a setup based on v4.X, you need to follow instructions documented on the v5 migration guide here. Do not sync the new code over your setup!! If you do that, you will be force to follow the migration guide to have your CC setup working again.
The merge was done to keep the community fork closer to the official code and take advantage of all security and stability improvements that are coming soon.
I also would like to use this post to ask you all one thing. If you are using the community fork, please don’t open issues on the official github repo. Engineering will work only on issues that happen with the standard codebase, not with custom code. I enabled the issues feature on the fork repo so you can create issues and get support from the community.
Disclaimer – The information contained in this blog post doesn’t represent the official Microsoft guidance or best practices. It is just the view of the author on current alternatives, implementations and workarounds for common issues and/or business needs. Please refer to official Microsoft documentation and evaluate carefully any steps, code or procedures documented herein. The author doesn’t offer any warranty. Use this information at your own risk.
June 17, 2022 at 6:50 pm
Se eu tenho a versão 1 do Company Communicator. Posso seguir o passo a passo do upgrade para a versão 5?
June 30, 2022 at 5:18 pm
Infelizmente não. O upgrade é da v4 para a v5. Recomendo reinstalar já na nova versão.
July 21, 2022 at 8:13 am
So im a little stuck, i was at this stage
so i had deployed the official version, and then updated to your repo, and replicated the permissions in the author app as the graph app.
July 21, 2022 at 8:15 am
Note that there is a small difference between the permissions you had before on the author app and now need on the graph app. Check the upgrade documentation
July 29, 2022 at 7:12 am
Yes i cleaned up the author app as the guide instructed, removed the redirect uri, removed the permissions , updated the OptionalClaims to null.
The next step would be to just sync from the app service ?
July 29, 2022 at 10:20 am
Cristiano, na sua versão não aparece a opção de “DELETE” após um comunicado ser enviado… é assim mesmo?
August 2, 2022 at 9:12 am
Do we have delete in the official version for sent messages? I don’t think so.
August 3, 2022 at 3:52 am
I dont need to redeploy the resources
using the Azure template after updating the Author and Graph App registrations correct ? Just Sync the code ?
August 3, 2022 at 7:42 pm
if you are using v4 you do need to run the template. The template will create an instance of Azure Key vault that is required for v5.
August 5, 2022 at 4:35 am
So my question here would be, will this be basically like a fresh install, will the existing resources be overwritten ? or will the missing Key Vault resource just added along with the existing resources ?