pk stuff

Here is a couple of neat tricks from Robert McClaws describing how to serve up a ASP.NET 2.0 folder – perfect for development and testing.

From the command line:
"C:WINDOWSMicrosoft.NETFrameworkv2.0.50727WebDev.WebServer.exe" /path:[PATH OF YOUR WEB APP] /port:[WEB PORT] /vpath:[/mywebapp]

Or to add a web server extension to Windows Explorer (so you can just right click the folder), add the following registry entries:

[HKEY_LOCAL_MACHINESOFTWAREClassesFoldershellVS2005 WebServer]
@=”ASP.NET 2.0 Web Server Here”

[HKEY_LOCAL_MACHINESOFTWAREClassesFoldershellVS2005 WebServercommand]
@=”C:WindowsMicrosoft.NETFrameworkv2.0.50727Webdev.WebServer.exe /port:8080 /path:”%1″”

Chris Frazier added this small program to work around some of the problems mentioned here with this trick:
using System;
using System.Windows.Forms;
using System.Diagnostics;

namespace OpenCassini
{
class Program
{
/// <summary>
/// The main entry point for the application.
/// </summary>
[STAThread]
static void Main(string[] args)
{
string path;

string command =
@”C:WINDOWSMicrosoft.NETFrameworkv2.0.50727WebDev.WebServer.EXE”;
string commandArgs = string.Empty;

Random r = new Random();

string port = r.Next(1024, 9000).ToString();

if(args.Length == 1){
//grab the original path
path = args[0];

commandArgs += ” /path:”” + path + “””;
commandArgs += ” /port:”;
commandArgs += port;
commandArgs += ” /vpath: “/”;
commandArgs += path.Substring(path.LastIndexOf(”) + 1);
commandArgs += “””;

System.Diagnostics.ProcessStartInfo info = new System.Diagnostics.ProcessStartInfo();

info.Arguments = commandArgs;
info.CreateNoWindow = true;
info.FileName = command;
info.UseShellExecute = false;
info.WorkingDirectory = command.Substring(0, command.LastIndexOf(”));

Process.Start(info);

using(Control c = new Control()){
Help.ShowHelp(c, “https://localhost:” + port + “/”);
}
}
}
}
}

From Sara Ford’s blog (tips and tricks for Visual Studio), this still works for VS 2008:

Remembering keyboard shortcuts can often be difficult but they can also save you quite a bit of time. If you go to Tools/Customize and check the option for Show shortcut keys in ScreenTips, then you’ll be reminded of the keyboard shortcut for any item on the toolbar when you hover over the icon.

SSH remote login without a key is fairly straightforward, here‘s one of many how-tos.

But the part I often forget is to set the permissions of ~/.ssh to 700 and authorized_keys to 600. More permissive settings, i.e. 775, will cause key-based login to fail.

In brief, generate a personal private/public key pair using ssh-keygen. Copy the  public key the remote system’s .ssh/authorized_keys file. You can now SSH to the remote systems without using a password.

On Amazon, Donald Mitchell summarizes lessons to be learned from Marshall Goldsmith’s book as follows:

“Letting winning get in the way of relationships you need;
Dropping too many ideas on those who work for you;
Being judgmental rather than helpful;
Slamming people in public or behind their backs;
Making comments that indicate you disagree with everyone that’s just been said;
Showing off how smart you think you are;
Saying anything in anger;
Being negative;
Keeping secret what others need to know;
Not recognizing the contributions others make;
Claiming undeserved credit;
Refusing to take responsibility for bad results;
Being focused on the past;
Favoring those who agree with you;
Not apologizing;
Ignoring what others are saying or shutting them up;
Being ungrateful;
Shooting the messenger who brings bad news;
Blaming others for everything;
Insisting on sticking with you bad habits after you’re aware of them.”

Of course, the hard part is recognizing this behavior in ourselves.

Wow!

It would have been nice to know that my Thinkpad T60 (and other systems systems using ATI’s proprietary fglrx drivers) would lose the ability to suspend or hibernate after following Ubuntu’s Update Manager’s suggestion to upgrade to Gutsy.

To make matters worse, this was no surprise to the Ubuntu team since community testers were complaining for months prior to Gutsy’s release. And the driver worked fine in Feisty: the issue seems to be related to rushed adoption of a new kernel memory allocator, despite widespread knowledge of lingering problems.

This is very disappointing coming just as more and more people are taking a serious look at desktop Linux.

Proposed solutions include: downgrade to Feisty (!!! – a warning not to upgrade in the first place would be better) or use the open source ATI driver. While I appreciate the incredible effort made by the open source developers, it is still dramatically slower than ATI’s, and effectively unusable with Compiz.

In fairness to Ubuntu, it seems Fedora and Suse are experiencing the same problems.