Migration is always pain in the… back.

I just took a quick look at my old posts. And I’m really upset with what I saw there. I’m not sure if this is because GeSHi is not working fine with WordPress, or is it caused by migration of posts between Windows Live platform and WordPress platform…

Anyway: all code I had on blog with ‘\’ is no presented without this sign. And I really don’t feel like updating it all to get it back where it should be. 😦

I’m not sure if that can be automated, I would guess not. Not really nice thing to have. So let’s give it a try, path in GeSHi using ‘/’ and ‘\’:

PowerShell, using GeSHi
  1. # First folder with modules in $env:PsModulePath:
  2. MOD1:\BSonPosh\BSonPosh.psm1
  3. # Second one…
  4. MOD2:\BitsTransfer\BitsTransfer.psd1
  5. # Last but not least (using / )
  6. MOD3:/ISEFun/ISEFun.psm1

Wonder what all those MOD# are all about? Well, I’ve decided that it will make it easier for me to psedit any module .psm1 file. I don’t have to remember paths to modules, I just have to test where (in which of MOD# drives) it is stored. And Get-PsDrive will help me with that:

PowerShell, using GeSHi
  1. PS C:\TEMP\PowerShell> Get-PSDrive MOD* | Format-Table name, root  -AutoSize
  3. Name Root                                                                   
  4. —- —-                                                                   
  5. MOD1 C:\Documents and Settings\bielawb\My Documents\WindowsPowerShell\Modules
  6. MOD2 C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\                    
  7. MOD3 C:\TEMP\PowerShell\Backup\Modules\           

OK. So now let us see what WordPress will do with my paths this time… 😉


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s