And in atelier it was possible to do what I said and they were used to work like that.
- Log in to post comments
And in atelier it was possible to do what I said and they were used to work like that.
In the end it is a decision of the place where I work. Also one of the reasons is that we have to connect to a VPN to access the server, and if we simply want to see a code it is time we can save. But as you say, there are no compelling reasons to have to do it as I said.
Okay, you're right. And how do I save the files locally and not update them on the server? So I can decide when to upload it.
The reason is to follow a dynamic similar to the one used in GIT. Each person works and saves his changes in local mode and once he has everything ready he uploads it to the repository. This avoids constant conflicts. And, finally, to be able to use the TFS to save versions of the classes.
yes, sorry for the misunderstanding
When I connect to the server, I export to my workspace the classes I want to modify, but every time I save it compiles and updates on the server, and I don't want that to happen. The ideal would be once exported the classes, not to have to connect to the server and to be able to work locally.