I have some specific questions about about how Acumatica developers manage customization projects, in particular those that involve custom C# classes and are developed using Visual Studio:
- How do you manage your code repository and versioning for Acumatica customizations? Would you recommend using the built-in Azure DevOps tools in Visual Studio to manage Acumatica customization code?
- Do you have any advice for maintaining multiple different versions of a customization project that correspond to different Acumatica builds?
- What’s the best way to manage multiple development sandbox instances for multiple clients? Is this usually done on a virtual machine?
- Do you have any general advice for QA / testing specifically in Acumatica? How would you set this up for a small team without a dedicated testing engineer?
Any insight or advice on these questions would be greatly appreciated!
Best answer by Gabriel Michaud
View original