Because of a new way of working here at the customer I'm located at, two virtual machines will be deployed to each developer's machine. These VM's will be run using VMware player. The thing is, the VM's should be able to access the network and all the 'normal' resources. Because of this, all the VM's should have unique (computer)names. But they have to be traceable to the host machine.
The wish the customer has at this point is to give the VM's a computername based on the name of the machine the VM will be run on. Unfortunately, this doesn't seem to be supported in VMware, other than using sysprep and asking the user to enter the host's computername. At this point the 'asking the user' option is being used, but we're trying to find a way to get host's name from within a VM without any user interaction. Nice challenge... ;)
The VM's are working like a charm. Dragging and dropping files between host and VM, supergood performance (of course, with a 2.16 GHz Core Duo 2Gb internal memory laptop....!) and seamless resizing of the entire VM desktop. My first impression tells me VMware player works smoother than Microsoft Virtual PC, but the comparison is uneven because of the state of the art hardware I'm running VMware on right now... If I have any more info, I'll keep you posted.
By the way, if you have any ideas about getting the host's name, drop me a
line.
Together with a colleague, I'm giving basic .Net training for colleagues at this moment. Not at THIS moment exactly, because they're doing exercises right now. But today is the second day of four days of training in total. Currently we already have two weird things popping up.
Last week we encountered significant inaccuracy when calculating values using doubles. For instance, when adding 0.1 to a double (instantiated at 0) several times, the value wondered off. After 3 or 4 times there was an inaccuracy of 2 or 3 in the last decimal. The difference is very very small, but it’s there… I knew there’s an inaccuracy in the representation of doubles, but I always thought it only occurred with difficult fractional values.
VB6 DLL’s are not always imported as you would expect. Visual Studio (2005) automatically generates interop assemblies when you reference a non .Net assembly. Today one of the course takers did this, which resulted in classes that didn’t have all the properties defined in the old DLL. There were two string properties having the exact same coding placed in different classes, and only one of them showed up in the interop assembly. Also, some properties showed up as properties, some showed up as methods (set_PropertyName()) and some of them didn’t show up at all. I’m currently investigating why, but it’s kind of weird…