|| Tuesday, January 25, 2005
After figuring out the previous problem (DLL dependencies), I decided to install the .NET Framework SDK into the VPC image (a Windows Server 2003). No such luck: "Extracting file failed. It is most likely caused by low memory (low disk space for swapping file) or corrupted Cabinet file." No, not again a memory issue...
Wait a second! That image has 400 megs of memory assigned plus a 1.2 gig growth limit for the swap file. That can't be. As usual, I used Google to search for solutions. One (older) suggestion was to update Windows Installer - I gave it a shot anyways, and installed Windows Installer 3.0. No change, but that was expected. At least I am now up2date in that respect.
To spare myself further waste of time, I decided to take the easy route and ran
on my XP box, copied the extracted setup files to the VPC image - and presto! The SDK is installing like a charm.
Once again it pays off to be in this game... erm industry for so long: I got a weird Fusion loading error for an assembly:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of
an invocation. ---> System.IO.FileNotFoundException: File or assembly name ConsoleControl,
or one of its dependencies, was not found.
File name: "ConsoleControl" at ConsolePad..ctor()
=== Pre-bind state information ===
LOG: DisplayName = ConsoleControl, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
LOG: Appbase = C:\SharpDevelop\Repository\SharpDevelop\bin\
LOG: Initial PrivatePath = NULL
Calling assembly : ConsoleAddin, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null.
LOG: Policy not being applied to reference at this time (private, custom, partial,
or location-based assembly bind).
LOG: Post-policy reference: ConsoleControl, Version=0.0.0.0, Culture=neutral,
LOG: Attempting download of new URL
The assembly of course was right smack where the above URL is pointing to. So what was going on? First, I mailed the dev - no such luck, it was working on his machine (as if I would care: "I don't care if it runs on your machine, we are not shipping your machine!", Software Testers Anonymous).
As the test machine is a non-SDK machine (runtime installed only), fuslogvw was also out of the question. Mer...veilleux. Fallback to tools a C++ programmer loves and knows: Dependency Walker. This guy produced the following output:
A-ha! The dev checked in an assembly that was written in C++ (and thus he had all the runtime assemblies on his box), but he forgot the two beauties msvcp71 and msvcr71. Chalk one up for the old dogs.
Installed the latest version of X1 Desktop Search today. Why ain't I using one of the free desktop search offerings you ask? I need support for Eudora Mail as well as Mozilla, not just Outlook as offered by the freebies. And the preview pane just rocks.
|| Friday, January 21, 2005
Better late than never (having sent this to myself last weekend via Webmail and not touched till today): Scriptomatic 2.0 is here. The description from the download is indeed very teasing:
A completely new version of the famous Scriptomatic, the utility that writes WMI scripts for you. (And, in the process, teaches you the fundamental concepts behind writing WMI scripts for yourself.) Unlike its predecessor, Scriptomatic 2.0 isn’t limited to writing just VBScript scripts; instead, Scriptomatic 2.0 can write scripts in Perl, Python, or JScript as well. In addition, Scriptomatic 2.0 gives you a host of new output formats to use when running scripts, including saving data as plain-text, as a stand-alone Web page, or even as XML. Scriptomatic 2.0 handles arrays, it converts dates to a more readable format, and it works with all the WMI classes on your computer; on top of all that, it also writes scripts that can be run against multiple machines.
Next Friday, the German ASP and .NET communities will converge in Bad Ischl, Austria, for their annual non-technical meeting: the Community Wintercamp 2005. On the agenda, so to speak: skiing, sledging, local hospitality (not to mix up with local hospitals!) and a lesson in beer brewing as well as consumption. It looks like the weather is very, very kind to us too: snow all over the place and it'll keep snowing for the next few days. Hooray!
In case you have been wondering "What is he doing?" - I have been busy preparing my three talks for the ASP konferenz and VS2005 konferenz respectively:
- ASP.NET 2.0 Master Pages and Themes
- ASP.NET 2.0 Membership and Security
- Visual Studio Team System Team Developer in-depth
|| Wednesday, January 19, 2005
On my list of things to check out: PostgreSQL 8.0.0. Let's see how this baby stacks up against competing database systems.
This download details changes (new as well as updated features) to the HTTP API in SP1 of Windows Server 2003. It describes:
- Improved Performance and Scalability
- Enhanced HTTP Error Logging
- HTTP API Kernel-Mode SSL Support
- HTTP API Parser Enhancements
- HTTP API Parser Exceptions
- WOW64 Support
|| Sunday, January 16, 2005
Bernhard came back from the holidays with a great idea for our next hole of .NET Golf on the code fairway (currently only German, but we do plan to offer the fairway to non-German communities). We have ironed out the details, and come up with a test implementation together with Mike (of #develop fame). Hopefully, we'll (Alex, that is) also be able to get the automated tester up and running for this hole. In closing: this time, we do have a grand prize for the winner!
So, if you are German speaking and an avid .NET programmer, come join us on the fairway!
|| Thursday, January 13, 2005
Basically, this job is as easy as:
- Dump the repository on the old server
- Load the dump into a new repository on the new server
Dumping is explained here, and I won't go into detail because I wasn't the one doing it, Roman did it (I ain't touching a BSD box, more harm than good would result).
However, step two is in my ballpark, because the repository is moving to a Windows box. Two commands and you are up and running again (it can take quite some time, especially if your dump is like mine - a little over 528 MB!)
svnadmin create c:\repositories\fidalgo
svnadmin load c:\repositories\fidalgo < "e:\fidalgo.dump"
All that is left to do now is to restore the configuration and hooks (details in my last blog post on Subversion)
In closing, credit where credit is due: I gathered some inspiration from the following blog entry: A Rank Amateur Upgrades His Subversion Repository
© Copyright 2021 Christoph Wille
newtelligence dasBlog 2.3.9074.18820