none
Excel Workbook (Team) Project - TFS multiple developers RRS feed

  • Question

  • I manage several small team projects (with TFS) centered around Excel solutions (Add-ins and the sort), and I'm trying to work out the best method to enable our Excel developers to work concurrently with our programmers as we move more towards a .Net based environment.

    Previously the programmers had developed some automation elements in VBA whilst the Excel developers created a model/simulation.  Once the programmers are done, they drop the .bas modules into the workbook.  Once some initial Named Ranges and buttons are set up in the workbook, the VBA development is often largely independent of Excel land development.

    Moving forward, we would like to break away from the limitations of VBA and move toward a source control managed .Net environment.  This is working great for some add-in type projects, but I'm unsure of how to enable our programmers to do the automation coding whilst simultaneously permitting the Excel developers to create the Workbook.

    VSTO doesn't seem to permit Share Workbook from within the Excel viewer, and TFS doesn't seem to allow workbooks to be merged.  For the most part we can work within the limitations of Shared Workbooks, but I'm not sure what the best approach is?

    Monday, June 24, 2013 1:01 AM

All replies

  • Hi QuinRiva,

    Thank you for posting in the MSDN Forum.

    I'm trying to involve some senior engineers into this issue and it will take some time. Your patience will be greatly appreciated.

    Sorry for any inconvenience and have a nice day!

    Best regards,


    Quist Zhang [MSFT]
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Tuesday, June 25, 2013 11:41 AM
    Moderator