VMware Player - Virtual Network Editor

by plykkegaard 2. januar 2011 19:55

The Virtual Network Editor (vmnetcfg.exe) is not extracted during the installation and it is really needed if you want to mess around with the virtual network settings on the host OS.
It is a problem if you have different network adapters installed, like eg Bluetooth, WiFi, Hamachi etc

Extract cab files

You can extract all files from the installation by using the option /e and a destination folder is supplied

C:\Download\vmware>VMware-player-3.1.3-324285.exe /e .\extract

Change to the subfolder and find the file network.cab, open it in eg Izarch and extract vmnetcfg.exe to the vmware player installation folder. You can also create a shortcut in your list of program files if needed

Tags: ,

VMware

Expand your vmware disks

by plykkegaard 25. december 2010 14:55

I have used VMware Workstation and - Viewer for testing, development, deployment and maintenance during quite a few years. Great product for this.

From time to time I have been in need of expanding the disks on the virtual machine as they have been almost out of free space. With VMware it's quite easy to do using the free standalone Converter.

With VMware vCenter Converter you can take copies of your virtual machine and change the disksize during the process.

There's a few steps where you need to pay attention otherwise the process is straight forward

  • Select source
  • Let the converter read the configuration
  • Choose destination
  • And alter the options a little ...

The converter suggest "Copy all disks and maintain layout", change this to "Select volumes to copy" and you can set new disksize for each disk.

Type the new disksize in GB and watch while the converter does the all the hard work or go and grab a cop of coffee while you're waiting

Tags: ,

VMware

Installing BlogEngine RC 2.0

by plykkegaard 18. december 2010 23:44

It's fairly stragiht forward to install BlogEngine, just follow the instructions ind the readme files and you're fine. Remember to set filepermissions on the app_data folder, files and sub folders etc.

If you're running in a hosted enviroment you might encounter an error: "unable to generate a temporary class". After some poking around on the internet I found that the XmlSerializer just might be the cause of the and I also found a quick and easy fix

As the asp.net windows user probably does not have the prober rights to create files in the windows temp folder. Solution is to point the XmlSerializer to another folder for storing files/classes on the fly

Change temp folder

In the web.config I added this section

<system.xml.serialization>
    <xmlSerializer tempFilesLocation="d:\websites\blognet.web\app_data\temp"/>
</system.xml.serialization>

Obviously "d:\websites\blognet.web\app_data\temp" should reflect the correct path to your installation of BE
The method Request.PhysicalApplicationPath should give you a fairly good idea
NB! My installation has a different path too :)

All credits for this solution goes to http://www.hanselman.com/blog/changingwhere%20xmlserializeroutputstemporaryassemblies.aspx

Tags: ,

BlogEngine

License

All work downloaded from this site are licensed under the GNU AGPLv3 License

Calendar

<<  juni 2017  >>
mationtofr
2930311234
567891011
12131415161718
19202122232425
262728293012
3456789

View posts in large calendar

About me

I am yet another .NET developer (C#), experienced in various integration projects
  • Datacollection in the warehouse using pick by voice (VoCollect) or rf scanners (Psion Teklogix)
  • Electronic data exchange using Biztalk 2006 R2
Other cool stuff I have worked with in the past and present and will be working with in future

RecentPosts

RecentComments

None

Tracking