You may have heard about this in a recent Dot Net Rocks show already, but I found it interesting enough to do some link blogging :)
Xiine is a wpf based reader which allows you to read different sources (magazines, rss, etc) in a single reader application.
Xiine offers a very interesting take on (paying) published media, currently only code magazine. You can access the issues of the magazine (which you are entitled to) via the reader.
The interview, like most DNR tv/podcast episodes is recommend material :)
Wednesday, 8 August 2007
Breaking the build.. AnkhSVN style
At my current project (at an undisclosed governmental company) we are using Subversion as the source control software.
This is my first experience using Subversion, I’m coming from a pure SourceSafe background.
Regardless of the difference in terminology (You mean I got to do an update to get the latest version of the code?) the overall experience has been quite allright. Committing code is sometimes difficult, as the code on the server has changed already, so you need to merge the two changesets and recompile, but all in all, there’s nothing I can’t live with.
Enter the developer training. As the attending Source Control Guru told me: “The Ankh SVN plugin is a must have for any developer who wants to be productive, as it offers visual studio integration for Subversion.”
This sounded like music to my ears, and I made the clever (sic) assumption that the guru would know what he was talking about.
Once I got back to my development computer I promptly installed the Ankh SVN plugin, which while originally being built for VS.Net, also works for VS 2005. And this is where life started going downhill …
I added two new classes to my solution, which were cleary marked with a little plus sign.
A few minutes later I performed a commit on solution level, after which Ankh showed these classes as being commit and up to date.
A couple of hours later I did an update on the entire project, built the entire thing again and life was a-okay.
I went home, unsuspecting…
The next day when I arrived I was greeted by the build team, who told me that I had broken the build!
After my initial wtf I got into debug mode
- updated the code from the repository
- did a local build
and everything was fine.
I next checked the build team’s computer and saw that they were missing a couple of files, specifically the files I added the day before.
Checking the repository & the log it became clear that the files never made it into Subversion in the first place.
Which is weird, to say the least, as they are clearly marked as up to date in VS (ankh plugin) and in windows explorer.
It seems that Ankh messed up the .svn state!
So in short: if you’re using VS 2005 stay away from the ankh plugin!
This is my first experience using Subversion, I’m coming from a pure SourceSafe background.
Regardless of the difference in terminology (You mean I got to do an update to get the latest version of the code?) the overall experience has been quite allright. Committing code is sometimes difficult, as the code on the server has changed already, so you need to merge the two changesets and recompile, but all in all, there’s nothing I can’t live with.
Enter the developer training. As the attending Source Control Guru told me: “The Ankh SVN plugin is a must have for any developer who wants to be productive, as it offers visual studio integration for Subversion.”
This sounded like music to my ears, and I made the clever (sic) assumption that the guru would know what he was talking about.
Once I got back to my development computer I promptly installed the Ankh SVN plugin, which while originally being built for VS.Net, also works for VS 2005. And this is where life started going downhill …
I added two new classes to my solution, which were cleary marked with a little plus sign.
A few minutes later I performed a commit on solution level, after which Ankh showed these classes as being commit and up to date.
A couple of hours later I did an update on the entire project, built the entire thing again and life was a-okay.
I went home, unsuspecting…
The next day when I arrived I was greeted by the build team, who told me that I had broken the build!
After my initial wtf I got into debug mode
- updated the code from the repository
- did a local build
and everything was fine.
I next checked the build team’s computer and saw that they were missing a couple of files, specifically the files I added the day before.
Checking the repository & the log it became clear that the files never made it into Subversion in the first place.
Which is weird, to say the least, as they are clearly marked as up to date in VS (ankh plugin) and in windows explorer.
It seems that Ankh messed up the .svn state!
So in short: if you’re using VS 2005 stay away from the ankh plugin!
Subscribe to:
Posts (Atom)
