Man siger jo at på et eller andet tidspunkt skal drengedrømmen udleves. Nu har jeg valgt at udleve min drengedrøm. Da jeg fik kørekort til bil i 1976 tog jeg lige efter, til en motorcykel kørelærer for at spare teorien, som man jo kunne dengang. Men det skulle vise sig at være en elendig kørelærer, som hver eneste time, sendte os frem og tilbage mellem to rundkørsler i den indre by, mens han sad i sit baglokale og drak øl. Jeg stoppede ret hurtigt hos ham og fik så ikke et MC kørekort dengang. Der er sket meget indenfor MC kørekort kursus siden da, og sidste år tog jeg endelig kørekort til MC og det var en helt anden oplevelse. Siden da har jeg købt en Honda Magna 750cc fra 1994, og hvilken maskine!!.

Læs mere om min motorcykel her

I have been writing a ScrewTurn plugin and have had my problem debugging it.

I read the ScrewTurn articles on debugging plugins, and find it annoying to include my code in the ST core just to be able to debug my code.

I worked a bit with an alternative setup, and found this alternative method I would like to share. It involves three steps

• Include the plugin project in the Screwturn solution.
• Create a post build event in the plugin project.
• Fix one line of code in the screwturn source, that will not affect the use of screwturn at all.
  

This method og debugging, separates the screwturn code completely from the plugin code. The method doesn't alter how ScrewTurn works at all. You can add new and remove finished plugin projects as you wish without changing a line of ScrewTurn code.

You can even update the ScrewTurns sourcecode, either with a fresh set of sources, or by adding minor updates, just remember to keep the assembly loader to load the pdb files also, as described below.

What I have done is¶

1) I have a folder with the screwturn code, where the ST solution file also exists. At some other folder I have a plugin project that references the ST pluginframework code. I have also added my plugin project to the screwturn solutiuon. There is no need to move the plugin project to the screwturn solution path.

2) In my plugin project properties page, I have create a post build event, that copies the result (binaries) of my plugin project into the correct locations of the screwturn website. This post build event code is generic, since it references the plugins path with $(Target*) and the ST solution with $(SolutionDir) so it doesn't matter how these are placed, for you to use this exact code without changes.

copy /Y "$(TargetPath)" "$(SolutionDir)WebApplication\public\Plugins"
copy /Y "$(TargetDir)$(TargetName).pdb" "$(SolutionDir)WebApplication\public\Plugins"

3) I then changed one ST core code line to load the PDB file also, as shown below:

from:

asm = Assembly.Load(LoadAssemblyFromProvider(Path.GetFileName(assembly)));

to:

asm = Assembly.Load(
         LoadAssemblyFromProvider(Path.GetFileName(assembly)), 
         LoadAssemblyFromProvider(Path.GetFileNameWithoutExtension(assembly)+".pdb")
      );

The line is located in the core project in the file ProviderLoader a few lines down in method LoadFrom, that is exactly in line number 242 for ST version 3.0.3.555.


This method of debugging make a nice separation between the plugin code and the screwturn code. I hope this may be a help to others to easier debug plugins.

I find the tables in Screwturn hard to use. Other than me have experienced this also, because the Screwturn team have indicated that they are loking for a new syntax to create tables.

Meanwhile I have turned to JQuery/JavaScript and Snippets to enter tabular data easily.



Read my page on the subject how i do this.

I was working on a project where a Wiki was used for dokumentation of other IT systems. Since the wiki is to be used mainly by technical staff, I just needed a way to make a quick intro to the wiki, without too much efford.

So, I made a quick tutorial for the Screwturn wiki that shows a few pages that explains about the various elements on the wiki page and the global functions. Like, where is the navigation menu, how to create a new page, how to edit a section of a page, what are categories etc.

Read my page on the subject where I explain in detail how I did it.

HTC's Desire and other new HTC mobiles with the Sense UI, have built-in widgets for controlling power usage, like turning on and off Wireless or Bluetooth.

One of these widgets are called Powercontrol. When this is added you may with a single touch turn on and off various powerhungry hardware elements.

These are WiFi, Bluetooth, GPS, Auto synchronisation and Screen light.

But, I was wondering how to turn on and off Mobile network. And I realized that is was also possible fairly easy, but still not with a single touch.

Hold down the power button, until the powermenu appear. In this menu you have the option of turning on and off mobile networking.

I have successfully installed Froyo on Desire and did not experience any problems.

During the first try I was stopped in process by a 25 Mb free RAM requirement. I needed to uninstall a few programs and Google Earth alone takes a lot but is easy to re-install.

All settings and data is kept and all downloaded programs still work after the update.

I find my phone somewhat faster but it may be a wish, that it has to be so.

I expect a lot more battery lifetime now, since processing is much faster, then the CPU should work much less, which in the end must improve battery life.

Update¶

Battery time has not improved im sorry to say. Battery time seems to be the same. I find it rather strange. A four times faster program must be using 1/4 active CPU time, which in turn should be positive on power usage.

Update 2¶

I have not really experienced any improvements in speed. Response times are mostly the same when using the phone in daily use. I have not really experienced much change even though there should be drastic changes in the kernel.

Enhver der har at gøre med administrative opgaver i Windows vil snart skulle bruge PowerShell i stedet for bedstefar DOS.

Jeg er allerede startet med Powershell og det er både sjovt og interessant. Det er interessant fordi PowerShell er meget anderledes i struktur i forhold til alle andre programmeringssprog jeg nogensinde er stødt på.

Kort fortalt er det sådan at alle slags data omdannes til objekter som kan samles i lister. En sådan liste kan sendes igennem et antal kommandoer som hver gør noget (filtrerer, beregner, konverterer) ved hvert objekt i listen. Det der kommer ud i den anden ende, kan til sidst sendes til et output (fil, skærm, netværk osv.) eller gemmes som en ny liste (variabel) til senere brug.

Se mit network monitor script, som logger i en fil, hvem der forbinder sig til hvilken port på din server.