Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "tfs"
when your company doesn't let you use source control because it's afraid people would steal the code 😩20
- Merging 300 files from one branch to another in TFS.
- No merge conflicts.
My first thought:
This can't be right. I must have done something wrong...3
I've had many, but this is one of my favorite "OK, I'm getting fired for this" moments.
A new team in charge of source control and development standards came up with a 20 page work-instruction document for the new TFS source control structure.
The source control kingpin came from semi-large military contract company where taking a piss was probably outlined somewhere.
Maybe twice, I merged down from a release branch when I should have merged down from a dev branch, which "messed up" the flow of code that one team was working on.
Each time I was 'coached' and reminded on page 13, paragraph 5, sub-section C ... "When merging down from release, you must verify no other teams are working
on branches...blah blah blah..and if they have pending changes, use a shelfset and document the changes using Document A234-B..."
A fellow dev overheard the kingpin and the department manager in the breakroom saying if I messed up TFS one more time, I was gone.
Wasn't two days later I needed to merge up some new files to Main, and 'something' happened in TFS and a couple of files didn't get merged up. No errors, nothing.
Another team was waiting on me, so I simply added the files directly into Main. Unknown to me, the kingpin had a specific alert in TFS to notify him when someone added
files directly into Main, and I get a visit.
KP: "Did you add a couple of files directly into Main?"
Me:"Yes, I don't what happened, but the files never made it from my branch, to dev, to the review shelfset, and then to Main. I never got an error, but since
they were new files and adding a new feature, they never broke a build. Adding the files directly allowed the Web team to finish their project and deploy the
site this morning."
KP: "That is in direct violation of the standard. Didn't you read the documentation?"
Me: "Uh...well...um..yes, but that is an oddly specific case. I didn't think I hurt any.."
KP: "Ha ha...hurt? That's why we have standards. The document clearly states on page 18, paragraph 9, no files may ever be created in Main."
Me: "Really? I don't remember reading that."
<I navigate to the document, page 18, paragraph 9>
Me: "Um...no, it doesn't say that. The document only talks about merging process from a lower branch to Main."
KP: "Exactly. It is forbidden to create files directly in Main."
Me: "No, doesn't say that anywhere."
KP: "That is the spirit of the document. You violated the spirit of what we're trying to accomplish here."
Me: "You gotta be fracking kidding me."
KP grumbles something, goes back to his desk. Maybe a minute later he leaves the IS office, and the department manager leaves his office.
It was after 5:00PM, they never came back, so I headed home worried if I had a job in the morning.
I decided to come in a little early to snoop around, I knew where HR kept their terminated employee documents, and my badge wouldn't let me in the building.
It was a shift change, so was able to walk in with the warehouse workers in another part of the building (many knew me, so nothing seemed that odd), and to my desk.
I tried to log into my computer...account locked. Oh crap..this was it. I'm done. I fill my computer backpack with as much personal items as I could, and started down the hallway when I meet one of our FS accountants.
L: "Hey, did your card let you in the building this morning? Mine didn't work. I had to walk around to the warehouse entrance and my computer account is locked. None of us can get into the system."
*whew!* is an understatement. Found out later the user account server crashed, which locked out everybody.
Never found out what kingpin and the dev manager left to talk about, but I at least still had a job.15
FML. All those "train your own object detection" articles can go burn in hell. Not even TFs pertained models work!11
me: "so what version control system + tool you're using for this website?"
co-worker: "what is version control?"
me: "uh... like tfs, you manage changes, merge etc!???"
co-worker: "ah, i'm using filezilla."3
I swear I work with mentally deranged lunatics.
Dev is/was using TFS's web api to read some config stuff..
Ralph: "Ugh..this is driving me crazy. I've spent all day trying to read this string from TFS and it is not working"
Me: "Um, reading a string from an web api is pretty easy, what's the problem?"
Ralph: "I'm executing the call in a 'using' statement and cannot return the stream."
Me: "Why do you need to return a stream? Return the object you are looking for."
Ralph: "Its not that easy. You can return anything from TFS. All you get back is a stream. Could be XML, JSON, text file, image, anything."
Me: "What are you trying to return?"
Ralph: "XML config. If I use XDoc, the stream works fine, but when I step into each byte from the stream, I the first three bytes have weird characters. I shouldn't have to skip the first three bytes to get the data. I spent maybe 5 hours yesterday digging around the .Net stream readers used in XDoc trying to figure out how it skips the first few bytes."
Me: "Wow...I would have used XDoc and been done and not worried about that other junk."
Ralph: "But I don't know the stream is XML. That's what I need to figure out."
Me: "What is there to figure out? You do know. Its your request. You are requesting a XML config."
Ralph: "No, the request can be anything. What if Sam requests an image? XDoc isn't going to work."
Me: "Is that a use-case? Sam requesting an image?"
Ralph: "Uh..I don't know...he could"
Me: "Sounds like your spending a lot of time doing premature optimization. You know what your accessing TFS for, if it's XML, return XML. If it's an image, return an image. Something new comes along, modify the code to handle it. Eazy peezy."
<boss walks in from a meeting>
Boss: "Whats up guys?"
Ralph: "You know the problem with TFS and not being able to stream the data I had all day yesterday? I finally figured it out. I need to keep this TFS reader simple. I'll start with the XML configs and if we more readers later, we can add them."
Boss: "Oh yea, always start simple and add complexity only when you need it."
Frack...Frack..Frack...you played some victim complaining to anyone who would listen yesterday (which I mostly ignored) about reading data from TFS was this monumental problem no one could solve, then you start complaining to me, I don't fall for the BS, then tell the boss the solution was your idea?
Lunatic or genius? Wally would be proud.4
While working with an older programmer,
Me: "Hey Randall, get latest version, I made a checkin"
10 minutes later...
Me: "Hey Randall did my fix work for you?"
Randall: "I'm still going through TFS looking for NO's"
Look at his screen, he is manually going through the file structure, checking the version of each file
Me: "You know you can get latest version of the folder"
Randall: "You can't always trust that, I've had problems with it in the past"
Me: (insert hair pull emoji)2
What.. the actual... fuuuuuck?!
Browsing through changes on TFS (yeah, yeah boo me for using TFS instead of git if you like, I don't care, most people use/prefer TFS here, so I conform 'to the standards'..)
Anyhow, going through changes, looking for the one where some comment appeared..
'a wild comment appeared'.. tadaaah!
Checked the rest of changes.. Hm.. Someone did a validity check.. that returns the 'false' if not passed.
// OK, great! They are finally testing their shit and fixing stuff..
But apparently then they decided it is OK to do all the shit anyways.. so WTF?!
Why even bother validating it?! Oh yeah, forgot... cuz in case it returned false YOU WERE NOT SUPPOSED TO LET SOME STUFF HAPPEN!! But they weren't assigned with that exact task I guess..
- do the validation algo // fml, not going into how fucked up that was written..but it was horrible!
- do validity check where appropriate/needed
- test validity check and that it doesn't break functionality
+ check if the validation actually logically works?! nope, not on my to do list, not my job..
All done, better not actually do something that requires you to think.. :\
How the fuck that happened?! How can one person be assigned to check if something is stupid/wrong?! and when checking (&confirming) still lets the customer do that shit anyways?! What's the point?! O.O13
Past two days one of the senior devs has been complaining to anyone who will listen about a UI assembly containing 'hard-coded' references to a third party component causing several builds to break. The developer who added the telerik component probably had no idea the reference is pointing to his personal directory instead of a relative path. Easy fix? Uh...yea...but he just ranted to our boss for about 10 minutes about he has no idea how to fix the problem and the TFS build failure holding up his other projects.
WTF!? You fracking know what the relative path is!...just fracking change it and move the frack on.
The drama this drama-queen keeps spewing out is driving me out of my mind.3
I was checking out this wk139 rants & thinking to myself how does one have a dev enemy.. o.O Well TIL that maaaaybe I have one too..
Not sure if ex coworker was a bit 'weird & unskillful' or wanted to intentionally harm us and thank god failed miserably..
I decided to finally cleanup his workspace today: he had a bad habit of having almost all files in solution checked out to himself, most of them containing no changes whatsoever... I reminded him on many occasions that this is bad practice & to only have checked out files he was currently working on. And never checkin files without changes.. Ofc didn't listen.. managed to checkin over 100 files one time, most of which had no changes & some even had alerts for debugging in them.. which ofc made it to the client server.. :/
On one or two occasions I already logged in and wanted to check if files have any real changes that I'd actually want to keep, but gave up after 40 or so files in a batch that were either same or full of sh..
Anyhow today I decided I will discard everything, as the codebase changed a lot since he left an I know I already fixed a lot of his tasks.. I logged in, did the undo pending changes and then proceed to open source control explorer.
While I was cleaning up his workspace, I figured I could test what will happen if I request changeset xy and shelveset yy, will it be ok, or do I have to modify something else & merge code.. Figured using his workspace that was already set up for testing would be easier, faster & less 'stressful' than creating another one on my computer, change IIS settings and all just, to test this merge..
Boy was I wrong.. upon opening source control explorer, I was greeted by a lot of little red Xes staring back at me... more than half the folders on TFS were marked for deletion.. o.O
Now I'm not sure if he wanted to fuck me up when he left or was just 'stupid' when it comes to TFS. O.O
So...maybe I do have a dev enemy after all.. or I don't.. Can't decide.. all I know for sure is tomorrow I'm creating another workspace to test this and I'm not touching his computer ever again.. O.O
I changed "Bug" in TFS to "Monstrous Hideous Defect". That'll get the mindset right. The word bug is so common that nobody cares anymore. New Monstrous Hideous Defect? Holy crap, better fix that right away! 😃
So this is my first rant but I have to rant about this because I can’t take it anymore.
So I have a manager that has build the department we are in from an application he built that takes care of department metrics. I work for an ISP for a technical support department that takes care of the metrics and tools that they use to troubleshoot(not to mention that I work mostly with shitty legacy code). When I first got into the team There was no version control, no way to actually measure our work and no actual structure on anything. So when I came in I implemented TFS and GIT, so now we have at least that. The problem is that when my manager decided it would be a good idea to implement agile/ Kanban development in my team, he also decided that a methodology that was proven to work was not enough. So he started adding a bunch of useless and annoying rules on top of that methodology. Some of those rules were for example we don’t use tasks, we use backlog items as tasks and each backlog item has to take minimum of 15 minutes and maximum of 2 days to get completed, if it takes you longer you have to split it into chunks like part A and part B etc. Same thing for features which don’t represent features but represent projects which can’t be greater than 2 weeks and then Epics which can’t be greater than 2 months. But also you can only put in TFS stuff that is related to projects and nothing else. So not all the work you do is accounted in there but yet it will be used for your overall performance at the end of the year. It’s fucking wack and I can’t wait to move out of there, the environment is pretty toxic. It feels like everyone in our team except the one ass licker is just dead inside and no one gives a shit anymore. And that is what happens when you try to make a proven working thing into something “better” when you know nothing about it.2
Follow up on a previous rant:
I visited a customer to talk about the reporting discrepancy between two applications.
It turns out the applications were custom built by outsourced developers from Russia, that communicate with each other through a byzantine (and completely undocumented) series of web services, excel import/export tasks, and a customized SSRS environment.
These are spread across at least half a dozen servers, some on-premise and some cloud based, there are at least 3 SQL servers (2 running 2005, one running 2000), a 10 year old local install of TFS (which no one knows a username/password for), and who-knows-what-else.
They laid off their entire IT team years ago, and they have no backups.
I'm not certain anyone there even understands what the software is supposed to be doing beyond the most general terms.
No one knows if they even have source code.
Biggest case of "nope!" I've encountered in more than 20 years of IT experience.1
Why is it so hard to convice coworkers (other programmers) to use source control? Yes it's an extra step every day or so but it can be so helpful and save so much more time tracking down versions and when the bug first appeared. Also, piece of mind if your computer every gets hosed.7
Does anyone here have experience with AWS CodeCommit?
Do you like it compared to other popular tools like github/gitlab/bitbucket/tfs?
I just started playing with it today and think it's pretty neat, wanted to reach out to the community here and see if you guys/gals know of any gotcha's that you may have encountered?7
Started a job as a full stack developer. My first task was shocking! Do these small edits on this backend script that collects stuff from one database and edits the entries in another... piece of cake so far!
Here is the project on the TFS...
HOLD ON! IS THIS VISUAL BASIC?!!
I came here to do .Net framework development and .Net Standard... I wasn’t told that there will be VB, I have never used vb.net before.
Now... that I’m going to maintain this script in the future, I decided to rewrite it in C#, few things I learned on my journey of doing this:
1- There is an access modifier in VB called Friend
2- There is a data structure/type called Collection, it’s a value,key pair! Not key value pair... Value first, then key!!
3- Do you know how null is null everywhere?!! In VB they call it Nothing! Yes, as in...
if(myVar == nothing)
Asking the guy responsible for that choice... he thinks VB is easier to read than C#
I DONT WANT YOU TO READ IT, I WANT IT TO MAKE SENSE AND WORK WITH THE REST OF THE C# CODE WE HAVE!!9
Thank you microsoft. You clearly got that right. If someone knows how to make passwords secure, it's you.
... Is this what you wanted to hear? Because it looks like you have no idea what you're doing.1
Not sure if yelling at someone for not listening counts as a fight.. 🤔 since he wasn't listening..ever!!
But yeah, my ex coworker was a champion in not listening and doing stoooopid shit, from not following orders, to cheking in all the files in solution to tfs (no changes + debugging shit etc) which made it a nightmare to find and fix his bugs.. I just gave up talking to him alltogether since he only wasted my time and didn't listen to any advice/order..
"We don't use nuget, it isnt secure. We just put all the dll's into a nuget directory thats available to all of the users in the company."
"But that means your references are all broken and your packages.config are wrong? None of your solutions build that are in source."
"We don't check in solution files either. That causes clutter in TFS."2
So we have this team that deploys some code. We had a change in that code that "we" forgot about. Turns out, a dev on our team decided it would be cool to rename an endpoint. Why? Great question. Because. So this code gets deployed, but the call to that endpoint didn't get deployed. System 2 tries to call the endpoint, 404. We roll back, we're searching, after like an hour, we find it. We go to TFS to see who did it. The dev grabs my keyboard and starts checking diffs, somehow managing to skip their commit (from 5 months earlier). I take back my keyboard and *surprise* it was the commit that was skipped. WTF? Why did you rename that endpoint? What do you mean you didn't do it? It has your name right there!4
Starting a new project, I suggested using git instead of TFS(last project was TFS) to my boss. He said “It (the project) is VS based, so to keep things easier...”.
I don’t think basing your project around an IDE is a smart thing to do. I don’t even like TFS its caused quite a few problems for us and is much less smoother than git. Furthermore VS offers really good git integration!4
Well, it happened, my school managed to block SSH
It also means no more git, and if this shit isn't fixed I might be forced to use TFS
Whoop de doo11
I once had a manager who demanded I physically print all of the Kanban cards and tape them to the office whiteboard. I was told to move the cards across the board after they were moved in TFS. I still had to keep up with my other duties in the QA department too!
Despite that, I still stayed on board with the company (the pay was good, and the work was simple.) As a QA teeter, I uncovered a rather nasty security vulnerability that would have put all of our customers data at reach to anybody. I advised my manager, and was told - just ignore it and ship the code please. I refused.
I was threatened with being fired, verbally assaulted, and challenged at the most trivial ways in everything I did after that.
Jokes on him now. I work from home in my dream job, doing what I love, with a manager who actually gives a rats ass about my concerns.
Moral of the story here - you don't have to agree with your subordinates , but you do need to validate their concerns.4
In work we use TFS (no judgement please) but I love creating shelvesets with obtuse names like
"The Evil Is everywhere in here"
"I See the Devil in this Code"2
Im currently doing my first project as a junior dev. I'm working with asp.net core and I had only used regular asp.net before. The project owner who was the guy that used to own the company I work for had only asked me if i was versed in asp.net and said that it was what I was going to work with. So from the start I'm a little bumed out. The difference isn't enourmous, but still.
First day, he says that we are going to use TFS for version handling (god damnit) then he says he has started a bit and has done the first push... And we're missing files. But he's asleep by the time i do the pull (9 hour timezone difference).
Next day he has gotten all the files up and I also get to know that I will be working alone and still have to use TFS.
A few days later he tells me I'm gonna present the first version the next week...
Oh, and did I mention that this is for one of the biggest companies in the world that the very top managers will use. Including CEO, cto etc4
When you work for a multinational organization that's adopting scrum. We don't swarm, our PO isn't even in the same building, and one of your teammates hates git (loves TFS).
Fake it till you make it I guess?3
Used TFS for last 7 years and now have to use GIT. OMG Can't get my head wrapped around it. Everything is so confusing. Online articles don't help a beginner. Send help please. Started using Bitbucket with Sourcetree. Still learning. I hate to say this But I feel TFS is more intuitive. Maybe because I'm new to GIT.17
Time to remove access to tfs for the BA. She started adding work for us for features that don't have their requirements gathered yet.
Another BA just sent us an email today about it with just a generic "we need this now" urgency with no description, no requirements, no real functionality defined. The other one had access to tfs because she was working with us on a project, and was helping out with requirements. But it seems she's forgotten that you can't just slap imaginary things in.4
Mini witch hunt going on with broken builds last couple of weeks. Change satellite assembly/project A, breaks random unit test that hasn’t been changed for months and the TFS nazi sends out emails demanding the “broken” projects be fixed. Doesn’t matter the unit/integration tests are likely out dated and team responsible for the tests needs to fix it.
Yesterday I deleted some logging code out of a security assembly, broke an integration test that hasn’t needed to be ran since January (test database didn’t exist anymore).
I would have had to re-create the database, re-import the test data (not trivial), re-deploy a service using the test database…blah. All because I removed some logging code.
I deleted the gated check-in TFS build definition. Code check in … no sirens …whew! I win!
Dear JIRA... Fuck!
Why can't you offer integration with TFS? You used to! Now you'll go down in the bag of unused software. Right next to iTunes for Windows.1
Since the last update of the company antivirus some things became terribly slow, like IE dev tools, they are standard slow, but now they ere horribly slow, copying a 500MB file over the network to my pc now takes 10 minutes and the worst part is git. Git is unusably slow so i can't use git-tfs anymore and have to use standard TFS again.
And whenever all of this is happening there is always the same thing on the top spot of CPU usage 'trend micro unauthorized change prevention service'.
Oh how I hate that antivirus crap
I worked at my previous job about 8 years (hired out of school) and wasn't actively looking for a new one; I had a lot of freedom and liked my boss and colleagues, but the pay was mediocre and I was under a lot of pressure because I was the sole architect, engineer, and programmer for a good number of important applications.
Anyway, my brother-in-law told me that his employer was looking for a developer and that previous candidates fell through, and that the pay was a lot more and they're good about raises (which was like pulling teeth at my then-current job) so I applied and went for an interview.
They basically gave me an offer on the spot and wanted me to start in 2 weeks. I told them that it would be hard since I'd basically be cutting my boss's Achilles by leaving so soon and suddenly (just hiring someone would take at least a month, not counting getting applicants), but they were adamant, as the position had been vacant for a few months at that point. I got them to agree to 3 weeks and pulled the trigger, but offered to help out in my old position for a few months cause we had a big project in progress I was leading.
So the new job is great: it's a much younger office and I'm having more fun and there's a lot less pressure. Meanwhile, at the old job, the project I was leading got scrapped and the asked me to do other odds and ends until, after screwing something up I basically told them I'm done. They got a new guy quickly due to a lucky turn of events, but he couldn't pick up where I left off on a lot of projects: they're going to rewrite one because of it. My one colleague still likes to point out that I left without them having knowledge of my code (besides that I always said I'd answer questions, plus it's been 6 months now and my code is all on a TFS instance they all have access to).
I still feel a bit guilty even though I have no reason to.
Whoever decided that working with exclusive check-outs with teams in TFS was a good idea should be shot. What an absolute ball-ache!1
My manager is making my team fill the tasks' "completed work" field in TFS with the exact same amount of hours we were inside the company. This seems unrealistic and doesn't take in account our daily capacity of 6h. What do you guys think of this? What should I tell her to convince her otherwise? Please, help me!2
I updated NDK, which resulted in some critical errors, because of outdated Gradle used deprecated NDK features.
I read about it, and decided to fix it properly, not hacking around - updatig that old gradle 2.2 to 4.10.2.
I spend about 6 hours fixing all problems and warnings that gradle had because of that, and then some.
At the end, some things still didn't work, but i was clearly missing some code from version control. I clicked update and left it for an hour.
THIS FREAKING BUGGY TFS PLUGIN RUINED ALL MY FILES I N THE PROJECT. WHY ARE WE STILL USING THAT F*King TFS???
Literally, I'm left now with .iml files in folders.
And my updated gradle files are gone too.
I have received this email and I just can't believe how they are thinking!
Microsoft asks TFS git users to change their ssh git URL!
And finally the stunning statement, thank you for using ssh!2
Why on earth wouldn't they give up on TFS. GET LATEST VERSION doesn't get latest version nor does it tell you that there are conflicts.
At my company we recently made some restructuring of TFS, such as renaming folders and moving projects between folders. That all worked out very nicely - except that some files completely lost track of their history!12
I'm done. Fuck you TFS. If you provide me with an option to run scripts on deployment targets then please show me these sweet errors that somehow must occur as my script is not executed at all..3
I forked an collection/project on TFS so a team could do their own changes on one application and leave me alone. Yay Shadow IT. Now I have to figured out how to do pull requests to merge back into “master” without me doing all the work.4
Lost my changes twice now. First time was my own fault. Was in a hurry to pick up my son from daycare so I checked in my code and locked my computer before the code was actually checked in. So today when I took "Get latest" somehow my last code from yesterday vanished. So, I rewrote everything, but now there was some problem with service references, and building the solution failed. A colleague had a look into it, but he couldn't resolve the problem neither. Instead he accidentally made an undo changes on my code, so now my code is gone again. And the solution still doesn't build. I'm just a *leetle* frustrated right now :(3
Requested latest code from TFS server ... there goes the rest of my afternoon. 26 Errors, 470 warnings.
The *project* build succeeded so you decided to check in your code changes. OK? WRONG! Always build *the whole solution* before checking in code! Never check in something doesn't build unless you want to make me groan *making groaning noises*
Working on an ongoing task of speeding up one of our applications. Our TFS server sends a message to a Slack channel with the check-in comment each time someone checks in. Amusing myself by using a recurring theme of "The Tortoise and the Hare" fable to explain what I fixed by including the :rabbit2: and :turtle: tags in my TFS check-in comment.
I've been worrying about the following problem for months now and I don't find any solution. Maybe anybody of you can lead me the way.
We are developing a software suite which consists of a number of desktop applications:
* 12 applications written in C++; all over 20 years old; further development by 5 or 6 guys (one man armys) - mainly bugfixing, changes of law implementations, small features
* 2 applications we are currently writing in C#; completely new developments of existing C++ applications; scrum teams with at least 5 guys; this is, where we put our focus in
These applications (C++ and C#) are sharing some core assemblies and are interacting with each other. So they are not independent.
We organize them in a mono repository in one huge solution, which consists currently of about 500 projects.
* With all projects in one solution and through project references, Visual Studio takes care of the right build order
* Code navigation is superb - every single line of code is accessible - this makes refactoring easy
* Every developer can map the branch and build the whole suite locally
* Debugging on the local machine is easy
* DevOps pipeline is straight forward - it just have to build a single solution
* The huge solution is extremely slow.
* If you want to build the solution or you want to debug (which does essentially the same as a pre step) Visual Studio is building a lot of projects, although they haven't been changed. Their detection is buggy. So sometimes you wait 2 minutes until it starts the app. That slows us down a lot.
* Full builds need about an hour, because its building the same projects (even if they haven't been changed) over and over again (with ready made nuget packages this could be improved a lot I think)
* If a core team member changes some core apis, he is changing the calling code too, although he doesn't know the calling code, because another team has written it. I don't think, that's best practice and it doesn't scale.
* Often, a C# developer has to mess around with C++ building problems, because the C++ projects are in the same solution
* It gets more and more confusing and frustrating, because there is no clear organizational seperation between apps and nobody can't just focus on his app alone.
I was thinking about putting the whole framework and core projects in a new solution (around 100 projects). Then we could take all old C++ projects and put them also in a new solution (around 200 projects). This would leave the newer projects (new applications - C#) in the existing solution.
This should speed up things, and would be a first step to better seperation, BUT:
How should the integration process look like?
Scenario: Core team is changing an API in our framework
Current process: Because all projects are in the same solution, they change the calling code too. So it's immediately integrated and the app developers just have to do "get latest".
New process (?): Core team is providing the changes through a nuget package (new version). So does every developer now has to keep track of if there is a new package version and if yes, do the integration? And how can we coordinate the different teams, so they are upgrading all at the same time? Because we ship our applications as a suite, all apps has to use the same versions. Or should we automate the integration process? Is there a best practice?
I have to add, that our core team is making changes very frequently, so the integration process will have to happen often.
Thank you so much in advance!4
Got really happy that I could use the new Boolean work item templates fields in TFS 2017 after upgrading from 2015....Turned into bludgeoning my head against the keyboard when I realised Microsoft decided it was a great idea to not including any way of validating said Boolean field. Time to go back to using Yes/No drop downs, or resort to dirty hacks....
TFS, I love you. We've been in a relationship for a long time. I've never seen this before. Please don't do it again. If you feel you must do it again, can we talk about it? Maybe with a third party?
How does your team approach code reviews? What sort of processes/tools do you make use of?
Currently my team uses TFS (which I'm not a huge fan of). I'm trying to figure out how to track issues (requests) and the code review process.8
Got a new notebook for work, got all Projects from tfs and it's like every single project I want to build has false references
My new team for some reason always ask me to shelve (TFS) the biggest changes before making checkins to STAG.
I don't even have permissions to create branches and they don't want me to make multiple checkins just a big one at the end of the feature because they say it's confusing, which is something strange for me as I am used to commit frequently.
I had already told them why I wanted a branch but they don't want it...
Today was the day!
The guy that was testing my feature unshelved my changes to his local folder and then proceeded to click on undo changes.
It took a week of hard work to do it...
He asked me if it wasn't me, he doesn't even admit.
Now he's asking me if I can do it today....6
TFS did it again! Merged changes into something that doesn't build! So I had to undo my changes and lost an hour of work. Isn't the whole purpose of TFS to enable teams to work with the same code concurrently?6
I think I'm becoming an expert in alt aramaic.
Maybe hebrew. Or galic.
All languages would make more sense to me - although I don't know them - than TFS errors, C Sharp compiler errors or anything else coming from this vomitting, miserere suffering pile of garbage....
Hate. Is too nice....
Seriously, who invented this and thought it would make sense?3
So when at work I love working from Jira/TFS and having little interaction when i'm battling through Code/Documentation
But Next time my manager strolls over to my desk and kicks my chair i'm Gona King Leonidas his ass out the 3rd floor window
FFS please reach out via Lync if u are planning to come up and annoy my tits!!!!!!
Goddamn I hate TFVS. I'm working on PHP application where the code is stored on TFS. So far, I've been getting by using the VSTS plug in Microsoft supplies on PHPStorm. The plugin is buggy as hell, and I'm about fucking done with it. Apparently, PHPStorm doesn't save files when your committing. Unbeknownst to me, however, the most recent attempt failed, crashing the plugin. Of course, and the commit task is still running under the hood, so none of my work has been saved1
Wow why is TFS (with default settings) locking files and the whole solution for the whole team just when i change the code formating for better reading? I cant wait when we move to git or even svn1
Designers use Dreamweaver, developers use Visual Studio... only our stuff is in TFS. Beyond Compare gets a workout on deployments.
yeah sure, having all 5 devs only ever working directly on the production branch and not being allowed to save anything post-release unless it's an urgent bugfix sounds like a great idea
FICK YOU EDMX AND FUCK YOU TFS SOURCE CONTROL! JUST WASTED 2 HOURS OF MY LIFE TO CHANGE A FUCKING COLUMN NAME!
It’s almost 2018 just right fucking SQL and use git.1
The moment a trainer u made your boss hire tells u, that it's far from normal that the devs (me) setup the tfs themselves and add also Backlog items, Testcases etc, because PO and Team leader are thinking TFS is way to technical and an developer only tool...
Project released to dev environment... None of my changes are in there. Check the TFS check-in history and the check-ins aren't the code I wrote for specific items. Don't know why, or how. My life is a lie.1
looking for a bit of help.
Has anyone a recommended tutorial / introduction to .NET development, TFS and Visual Studio?
And - for later - a good reference for the datatypes / advanced topics / build system?
I'm starting to work on a Windows only DLL plugin and quite frankly - I'm lost.
TFS and Visual Studio is new to me and feels awkward...
And thx to experience I can understand most parts of code but the build system is unknown to me.
And a lot of the data types .NET has ...
Thanks in advance!4
Any opinions over TFS + MTM over HP QC in a Microsoft Dev environment?
Any idea if MTM can be used automate tests for SAP?