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.
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.
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
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:
you get a
XmlDocFileEventArgsobject 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
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.
is working on a reply...