Hi Lutz, Sorry to bug you again, but we’re moving forward on a project where we are consulting with a client who is setting up an agile development team to use 4D. They will be managing this team with Microsoft Team Foundation Server. I’m thinking that TFS should be able to serve as a repository for the 4D code (methods and forms) using the VC_Framework component that you have updated.
> We have been doing something similar for some time with the VC_Framework > component. The original version of the component doesn't support the > re-import of code so we extended it with an import function for methods. The > procedure is a bit inconvenient, you have to do an additional step (the > import) manually after checking out the code from the versioning system > (Mercurial in our case) but it works flawlessly. We use this workflow and the > vc_framework component since 4d V13. Look here if you are interested: > https://github.com/elutz/vc-framework-v17 > <https://github.com/elutz/vc-framework-v17> The part that isn’t completely clear to me is the Build/Release Management part. I’m trying to figure now is how to link code in the repository to TFS work items so that the release manifest that TFS produces includes all the methods and forms which are code complete and validated by QA. In your process, how do you know which methods to import? Tom Benedict ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
