ict.ken.be

We use this checklist whenever we need to setup a new nuget package, that way it will include tests, coverage, labelling and deployment.

• Create repository on server: hg init c:\Respository\Nugets\ken.X
• Clone repository to local machine using TortoiseHg
• Create new Project: Templates - Windows - Class Library - Create directory for Solution - ken.X
• Close solution and move everything up one directory (cause of clone) - ken.X.sln
• Add ken.Tools nuget package to solution
• Create default hg ignore file with *.suo *.user bin debug packages/ tools/
• Add new Class Library Project for testing: ken.X.Tests + add ken.XUnit
• Solution - Configuration Manager - New - 'Publish' copy from Release and create project configurations
• Update so output directory for Publish is release folder in ken.X.csproj
• Update so output directory for Publish is release folder in ken.X.Tests.csproj
• Add Import Project for build.config in ken.X.Tests.csproj (<Import Project="..\tools\build.config" />)
• Update assembly information for ken.X.Tests
• Update assembly information for ken.X and add InternalsVisible for ken.X.Tests
• Add nuspec file to ken.X
• Rebuild the test project with publish configuration to deploy the nuget.

To edit and reissue a request you can drag and drop it to the composer, but I couldn't find the shortcut key for this.

Steps to add this functionality behind the 'X' key:
(edit: changed this to X because the new fiddler uses E for breakpoints)

• Ctrl + r to open fiddler script
• In OnBoot() add: 

  FiddlerApplication.UI.lvSessions.add_KeyDown(HandleAKey);

• After this method add: 

  static function HandleAKey(Sender, theKey:KeyEventArgs) { 
      if (theKey.KeyData == Keys.X)
      {
             var oS: Session = FiddlerApplication.UI.GetFirstSelectedSession();
             if (null == oS) return;
             theKey.Handled = theKey.SuppressKeyPress = true;
             FiddlerApplication.DoComposeByCloning(oS);
      }
  }

• Restart fiddler

1. You check WinDirStat with options > show unknown and see that huge disk space is unknown
2. You remove system restore points and still see huge disk space in unknown
3. You run WinDirStat as an admin and the application hangs
4. You worry, if someone is proxing stuff through my computer
5. You use  Procmon to check the file activity and see that lots of files are written in C:\Windows\System32\config\ systemprofile\AppData\Local\ Microsoft\Windows\Temporary Internet Files\Content.IE5
6. Ah, IE again. You delete this files and realize that they are created faster than you delete.
7. You type one of the htm files and see Assembly Binding Log Entry
8. You realize you forgot to turn off Fuslogvw (and it somehow logs to this hidden folder wtf)
9. You open Fuslogvx and click settings > log disabled
10. You cleanup the milion of files mess you made, understanding why your computer was going slower lately
11. Priceless, well actually around 850 euros 

Probably the previous version of web platform installer was uninstalled correctly.

Use a tool like CCleaner to remove the corrupt entry or try using this Microsoft uninstaller tool: 

http://support.microsoft.com/mats/Program_Install_and_Uninstall/

The cache of the webplatform installer can be found at:

%LocalAppData%\Microsoft\Web Platform Installer\installers 

• Incoming Tests: methods that check the functionality of dependencies your project relies on.
• Outgoing Tests: methods that check the end functionality of your product
• Middleware: software that sits at the front of the back-end (eg. NodeJS, OWIN)
• Middle-end: software that sits at the back of the front-end (eg. BreezeJS)
• Spark: templated solution that can be used to speed up the startup of a project.
• Spike: proof of concept for one specific project.

"Working Software" is software that users are actually using. Until it's in use it is truly useless.

Woody Zuill