Yes, Shift Happens. But one thing which I don't get is why all of a sudden people start panicking. What's wrong in India and China being developing exponentially. :) Isn't it the same thing happened to US? Anyway's. enjoy the video.
I have seen books which can tell you all the theory about TFS. And yes, what will happen if you click on a button on Branching dialog....that too. But if you really want to know what exactly is TFS, don't just download and forget this guide posted on CodePlex which describes how TFS should be used in real projects. Excerpts from the site:
"This guide shows you how to make the most of Team Foundation Server. It starts with the end in mind, but shows you how to incrementally adopt TFS for your organization. It's a collaborative effort between patterns & practices, Team System team members, and industry experts"
patterns & practices: Team Development with Visual Studio Team Foundation Server - Home
I feel its really mean but still seems like the complete history is shown in this humorous clip. :)
I found these weird behaviors in SQL Server. Well, weird because I never expected it this way. And whoever I asked, even they thought its weird.
1. Let's say you have an INSERT statement something like this:
INSERT INTO SomeTable VALUES (Col1, Col2)
SELECT Val1, Val2 FROM SourceTable WHERE 1<>1
Now, the select statement is never going to return any row due to the where clause (always false) therefore, no new row in SomeTable table. So, if there is an AFTER INSERT trigger on SomeTable, what do you think about it. Should it fire? Remember, there is not going to be any insert.
If your answer is NO ( as it was mine and few others too), think again. Because it DOES fire. And that's why I call it weird.
2. Another situation. Lets have the same INSERT statement but without any WHERE clause. So the query will be something like this:
INSERT INTO SomeTable VALUES (Col1, Col2)
SELECT Val1, Val2 FROM SourceTable
Now, if SourceTable has, say, 100 records and there is an AFTER INSERT trigger, how many times that trigger should fire. Remember, there are going to be 100 new rows in SomeTable.
If you answer is 100 (as it was mine too, again), check Books Online once more. The trigger is going to fire ONLY once.
One thing to note in both situations is that the LOGICAL tables have the correct information. That said, INSERTED logical table is going to be empty in first example and it will have 100 rows in second one. So, these logical table are your best bet. This behavior is same for DELETE and UPDATE after trigger too. Means, if you execute a delete or update statement which will not affect any row, triggers will fire regardless and it will fire once per statement NOT per affected row.
Hope this will help you to avoid this trap. :)
Enjoy!
Well, its being a long time since I posted anything here. One excuse for that can be the incompetent blogger.com UI for posting blogs. Those browser based text editors hardly work and blogger UI went one step further and provides WYSIWYG editor.
That was really an excuse. :) And reason you might be knowing already. Yeah, its the work. I really don't know where do people use those SDLC jargons in real life they used to fight on in university. I see it all the time that people just try to get things in production no matter how.
Anyway's, reason for this post is not that. You know how it feels when you see/use a piece of software that looks beautiful, integrates well and actually works. For me, it feels really good. I feel like computers are not meant just to scratch your head on crashes. Ok, the piece of software I am talking about is Windows Live Writer (like you didn't get it from post title, already).
I came across this here, downloaded, configured with blogger and that's it. I am posting from it. Hardly 3 mins to get the thing working as its suppose to work. Kudos to the team.
Give it a try. Its really good.
Enjoy!
