Hello,
As the title suggests, we’ve run into an issue when trying to synchronize from TFS (TFS 2012 update3) when using VS C# projects.
Let me try to illustrate with an example.
Developer A - creates and checks-in using TFS :
- a Visual Studio Project (C#) added to the AOT
- a Job which references a class within the C# project to call a static method.
Developer B - Synchronizes TFS for that model (with the ‘Force’ option)
The synchronization tries to compile the Job. It fails because it hasn’t loaded the assembly from the VS project and, therefore, doesn’t recognize the namespace\class\method.
Regardless of how many times we try to Synchronize from TFS, the C# project doesn’t get compiled. Because it doesn’t get compiled, it doesn’t matter if we restart AX and/or the AOS before synchronizing TFS again (we’ve tried.)
We end up having to :
- Compile the VS C# Project.
- Restart AX (or restart the AOS when hot-swapping is disabled)
- Compile the job (or synchronize TFS again)
This is a bit tedious especially since it isn’t always obvious where the problem stems from (to the person synchronizing from TFS, especially if they haven’t been working on the same modules or objects).
At least, if the project doesn’t change too much, we don’t have to deal with the issue too often…
I would like to know if there’s a better way to get around this. I would have expected telling other developers something along the lines of : if the Synchronize fails, restart your AOS, and try synchronizing again.
Note : This is only a problem on our development environments (when we deploy on machines with model files, the assembly gets loaded right after the axutil-Import call, and the following full-compile works fine.)
I hope I was clear enough. Any help / hint / feedback is much appreciated.
Thanks!
Patric