Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Niclas Schumacher 67 posts 87 karma points
    Apr 09, 2014 @ 22:34
    Niclas Schumacher
    0

    Usync with team foundation

    hello.
    First of all, thanks for this package, help alot when developing multiple people on the same project. 

    We are using TFS to get source control on the project, but are there any way we can make sure that TFS catches changes on our def.config files ? 
    The def.config file dosn't get triggered as checked out / edited when usync edits the def file, so we need to go into the file and make a space or something to get TFS to see that there has been a change, so we can get that def.config file into our check-in. 
    Is there any why this can be done automaticly, so we dont need to keep track of which documenttypes we have modified when checking our changes in ? 

    Once agian, thanks for the package, and Good Job on having it ready for 7.1. 
    ps. It's the latest version of usync, 2.2 i think.

     

    - Niclas Schumacher

  • Kevin Jump 2309 posts 14673 karma points MVP 7x c-trib
    Apr 09, 2014 @ 23:02
    Kevin Jump
    0

    Hi

    Someone a while back had read-only issues checking into TFS so there are events in the uSync which should be just for what you need - to tie into TFS.

    when an individual config file is about to be saved / is then saved uSync will call the there is also a deleting/deleted event.

    so if you hook into the events:

    jumps.umbraco.usync.helpers.XmlDoc.Saving += XmlDoc_Saving;
    jumps.umbraco.usync.helpers.XmlDoc.Saved += XmlDoc_Saved;
    jumps.umbraco.usync.helpers.XmlDoc.Deleting += XmlDoc_Deleting;
    jumps.umbraco.usync.helpers.XmlDoc.Deleted += XmlDoc_Deleted;
    

    you get a XmlDocFileEventArgs object which has the path of the file being saved in (so from that you can work out if it's a doctype, datatype etc.

    on a load you might get a lot of these events fired so you might first want to hook into the startup events

    uSync.Starting += uSync_Starting;
    uSync.Initialized += uSync_Initialized;
    

    Starting is fired before usync does anything and initialized is fired when it's done it's finished at start up. so for example you might just want to hook into Initialized, and once that fires then hook into the individual events.

    hope that helps.

Please Sign in or register to post replies

Write your reply to:

Draft