I'm adding support for the new command-line switch for svnserve that lets you specify a config file that will be use for all your repositories. This is only available if you are using Subversion 1.5 and newer. Here's a screenie of that:
After much work reinstalling Vista and Visual Studio 2008, I found out that I still can't debug 32bit MMC 3.0 snapins in Vista 64. You still need to attach the debugger manually to the running process. Unfortunately, this means that you won't be able to debug stuff while your code is loading.
I really was not ready to go back to 32 bit, so I compromised by creating a VMWare image that contains Windows XP SP3, Visual Studio 2008 SP1, and all the other necessary dev tools.
I now have a rig that I know always lets me debug. TortoiseSVN makes it simple to keep my VM and desktop synched.
Score that a WIN!
SAPIEN Technologies recently released a free tool to create GUIs for your PowerShell cmdlets. Here's a blog post with a screenshot. It's called PrimalForm.
It can be downloaded from here. (quick registration needed)
Well, I found out that Visual Studio 2005 breakpoints do not work in Windows Vista 64bit. It is a known issue.
Just-In-Time (JIT) Debugging of an elevated process will fail
The workaround is to attach the debugger manually. Bummer! I think I'm going to migrate PainlessSVN to Visual Studio 2008. Thankfully, I already have it installed.
My employer's, The Generations Network (TGN), headquarters are in a very nice location. We are surrounded by mountains on 3 sides. I took some pictures with my new T-Mobile Shadow. The camera in this baby is much better than any of the other phones I've ever had. Almost better than the digital camera that we own too!
I put the pictures on their own page, so that they don't bog down the blog. Click on the title, then select the link that says "Next Page."
My workstation is finally back to "normal." I ended up having to get a new motherboard and cpu. This was frustrating because I had to change from AMD to Intel. All of the PC part stores have closed in my area. PC Computer and CompUSA were the biggest ones out here. Makes me wish we had a Fry's over here.
I didn't want to wait a week and a half to have something else mailed to me, so I went to a local reputable computer builder. I went to PC Laptops. They hooked me up with an Asus P5QL-EM mobo, and an Intel Core 2 Duo E7200 (2.53 GHz) cpu.
Total damage to my wallet was $383.56.
The most aggravating thing was that in the end, it was a flaky DIMM that caused all of the trouble. So now, I have a perfectly good AMD cpu and MSI mobo sitting on my office.
I now have an Acronis True Image with all of my stuff installed. So when this happens again, and you can bet that it will happen again, will get me going in about an hour.
I had a issue where I didn't know how in the heck to debug PainlessSVN in my new Windows Ultimate x64. Thankfully, I found the answer after only a couple Google queries.
MMC 3.0 comes in both x32 and x64 versions. Normally, I would call the mmc.exe host with just C:\Windows\System32\mmc.exe in the debug tab of the project properties. I found out that I needed to append a -32 parameter at the end of this path. Here is how it is setup in the tab:
That command-line argument that I highlighted in red is very important.
I found the answer in this blog post: http://blogs.technet.com/askperf/archive/2008/04/25/controlling-your-mmc-snap-ins-on-64-bit-operating-systems.aspx
I finally took the plunge and change the default colors for my Visual Studio text editor. I tried a few from http://idehotornot.ning.com I liked Pill Crusher 2008 the best. The nice thing about it is that it can be used in both VS2005 and VS2008. All that is needed is to open the settings in your favorite text editor, then change this node:
ApplicationIdentity version="9.0"
to this:
ApplicationIdentity version="8.0"
VS2005 is 8.0, while 9.0 is VS2008
I'm currently working on adding support for Subversion Realms to PainlessSVN. Here's a screen capture of what I have so far:
Here's the content pane set with a large icon view:
I'm running this in my new Vista Ultimate 64-bit OS.
Well, I got the hard drive yesterday. I got home from my day job and found it on my chair. Wife put it there before I got home.
So, I unpack the critter and install it in my rig. I turn it on... no POST message show on the screen. WTF?!? So I spent my evening plugging in components on the motherboard. I took a break to watch Ghost Hunters, then back to tinkering.
No luck so far. My next step is to unscrew the motherboard, and see if there is something shorting it. I did notice that I got some electrical shocks when I turned my rig on. Not all the time though.
If this fails, I'll have to spring for a new mobo. Not what I wanted. Oh well!
