locked
How to do Development in CRM 2011 usinf TFS ? RRS feed

  • Question

  • Hello,

    I want to know that is there any way to do the Development work in Ms Dynamics CRM 2011 using TFS Server. 

    If it is possible than Please let me know the way of doing this.


    If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful"

    Wednesday, June 26, 2013 9:58 AM

Answers

  • Hi,

    This always causes a challenge since much of the customisations are included in the solution xml and are not easily separably into separate source files. The key is to define your process and then ensure it is stuck to.

    The process I use is:

    1. I keep as much as possible in TFS through Visual Studio integration
         a. I use the Developer Tool kit to organise web resources, Silverlight, Plugins and workflow assemblies. (http://msdn.microsoft.com/en-us/library/hh372957.aspx)

         b. When developing JavaScript web-resources, Fiddler or a ‘redirect stub’ is used to ensure that the Javascript is loaded from the local disk whilst developing. Once finished, the files are all checked in to TFS (http://complexitykills.blogspot.co.uk/2013/02/fiddler-crm-and-javascript-time-saver.html)

         c. An msbuild script is then used to build and deploy webresources and assembles from the build server on a regular schedule or on demand as needed. Developers should NEVER be adding these TFS artefacts to the master server – it should only be done by the build server.

         d. In addition to this, you can also use the solution packager found in the sdk to get a more finer control over your solution element xml - http://msdn.microsoft.com/en-us/library/jj602997.aspx

    2. Artefacts that are not in TFS are the usual configuration items – Entities, Views, Forms, Roles, Ribbon Customisations, Workflows etc. All these are held on a ‘master’ organisation that devs must make changes to centrally. The build process exports the solution and checks it into TFS with every build. Before any changes are made, I use a ‘semaphore’ process where the Developer emails all the team members notifying them of the change so that no one makes a change to the same component at the same time.

    3. The solution on the master configuration solution is versioned by the build process (<Major>.<Minor>.<Build>) and then can be import into UAT/Production by getting the latest from Source control – or exporting it anew.

    4. Developers get the latest solution on a regular basis and import into their own development server and perform a Build/Deploy on the CRM Developer Toolkit Solution

    hth


    Scott Durow
    Blog www.develop1.net    Follow Me
    Rockstar365
    If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful"

    Wednesday, June 26, 2013 10:17 AM
    Answerer

All replies

  • Hi,

    This always causes a challenge since much of the customisations are included in the solution xml and are not easily separably into separate source files. The key is to define your process and then ensure it is stuck to.

    The process I use is:

    1. I keep as much as possible in TFS through Visual Studio integration
         a. I use the Developer Tool kit to organise web resources, Silverlight, Plugins and workflow assemblies. (http://msdn.microsoft.com/en-us/library/hh372957.aspx)

         b. When developing JavaScript web-resources, Fiddler or a ‘redirect stub’ is used to ensure that the Javascript is loaded from the local disk whilst developing. Once finished, the files are all checked in to TFS (http://complexitykills.blogspot.co.uk/2013/02/fiddler-crm-and-javascript-time-saver.html)

         c. An msbuild script is then used to build and deploy webresources and assembles from the build server on a regular schedule or on demand as needed. Developers should NEVER be adding these TFS artefacts to the master server – it should only be done by the build server.

         d. In addition to this, you can also use the solution packager found in the sdk to get a more finer control over your solution element xml - http://msdn.microsoft.com/en-us/library/jj602997.aspx

    2. Artefacts that are not in TFS are the usual configuration items – Entities, Views, Forms, Roles, Ribbon Customisations, Workflows etc. All these are held on a ‘master’ organisation that devs must make changes to centrally. The build process exports the solution and checks it into TFS with every build. Before any changes are made, I use a ‘semaphore’ process where the Developer emails all the team members notifying them of the change so that no one makes a change to the same component at the same time.

    3. The solution on the master configuration solution is versioned by the build process (<Major>.<Minor>.<Build>) and then can be import into UAT/Production by getting the latest from Source control – or exporting it anew.

    4. Developers get the latest solution on a regular basis and import into their own development server and perform a Build/Deploy on the CRM Developer Toolkit Solution

    hth


    Scott Durow
    Blog www.develop1.net    Follow Me
    Rockstar365
    If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful"

    Wednesday, June 26, 2013 10:17 AM
    Answerer
  • That's Great Scott.

    Thanks. :-)


    If this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful"

    Wednesday, June 26, 2013 12:20 PM