Exploring ASP.NET MVC

Code First method build from scratch

  • Make a backup of /Model files and /Migrations and delete xxx_Initial.cs one, delete all files under /Migrations, delete all tables in database
    Alternatively run: Update-Database -TargetMigration $InitialDatabase to roll back to what it was
  • Run enable-migations -Force in PM>
  • Change the /Migrations/configuration.cs file with file below – notepad
  • Run add-migration Initial in PM>
  • Run update-database in PM>
  • Check the database and all the class table in there as well Identity one (ASPNETxxx) and also the /Migration/xxxxxxxx_Initial.cs appearing with ASPNET as well.


  • The Designer Code for this migration file includes a snapshot of your current Code First model. This snapshot is used to calculate the changes to your model when you scaffold the next migration. If you make additional changes to your model that you want to include in this migration, then you can re-scaffold it by running ‘Add-Migration Initial’ again.




PowerShell accessing remote machine


The remote machine is running under Workgroup not as a Domain. The software updates such as Adobe Acrobat needs to  be updated manually due to the current standard user credential won’t let the system to install it (UAC) and it required Administrator account to login and run. The administrator has to logon every machine manually and run it the updates. The updates sometimes ran every week.



On the Remote machine

Start Windows PowerShell as an Administrator by right-clicking the Windows PowerShell shortcut and selecting Run as Administrator

At the PowerShell prompt, verify the WinRM is running by using the following command:

get-service winrm

The value of the Status property in the output should be Running.

To configure WIndows PowerShell for remoting, type the following command:

Enable-PSRemoting -force

If the remote computer is not in a trusted domain, the remote computer might not be able to authenticate the credentials. To enable to authentication, it requires to add the remote computer to the list of trusted host for the local machine in WinRM. To do so, type:

winrm set winrm/config/client ‘@{TrustedHosts=”LocalComputer”}’

On the local machine

Start Windows PowerShell as an Administrator by right-clicking the Windows PowerShell shortcut and selecting Run as Administrator

Run the following command:

winrm set winrm/config/client ‘@{TrustedHosts=”RemoteComputer”}’


winrm set winrm/config/client ‘@{TrustedHosts=”*”}’

Exit from this application.

Run Windows PowerShell ISE as Administrator

Create Untitled.ps1 document and save it under: C:\Users\Username\Documents

$Credentials = Get-Credential
Enter-PSSession -ComputerName RemoteComputer -Credential $Credentials

Run hostname to verify local machine

Run the Untitled.ps1 command with authentication window

Run hostname to verify that on remote machine





  1. Remote machine: Ms Windows 7 Professional
  2. Local machine: Ms Windows 7 Professional
  3. Network: Workgroup NOT domain


Updating Post Service Pack 3 Office 2003


Office 2003 is no longer supported, automatic updates is no longer working and there are lots of Office Updates 2003 after post Service Pack 3.


Download Office 2003 Update List (.ulz) file from this post (last updated November 2015) – http://www.msfn.org/board/topic/163238-post-sp3-updates-for-office-2003-updated-14-nov-2015/

Download and run Windows Updates Downloader – http://www.windowsupdatesdownloader.com/ProgramFiles.aspx