thomgerdes.com Report : Visit Site

Technical data of the thomgerdes.com

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host thomgerdes.com. Currently, hosted in United States and its service provider is Google Inc. .

tuugo.co.uk 

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called GSE containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

thursday, december 22, 2011 debugging metro style applications an metro style application needs to be packaged, signed, and deployed before it can be launched from the the windows desktop, as i discussed in my post on creating an appx package . this means an ide needs to go through a lot more work in order to launch an application for debugging than just calling createprocess with the debug_process flag set. creating a package for now, i'm just using createappx and the powershell cmdlets add-appxpackage and remove-appxpackage to manage my packages from batch scripts. ide integration should use the app packaging and deployment apis to achieve these steps. ipackagedebugsettings windows runtime internals: understanding "hello world" is a talk i've mentioned before as a must watch talk. a large part of what he does is debugging low level stuff with the provided command line debugger, cdb. i found this indispensable for getting started. in this talk he uses a tool that enables debugging on a package using ipackagedebugsettings. he shared this tool unofficially on codeplex , and then microsoft packaged an official sample on their own site . another package matt suggested you get is the windows developer preview symbols (for x86 and x64), which are available for download through msdn. these symbols are useful for debugging the internals of the windows libraries from cdb, windbg, or visual studio. it's handy being able to put breakpoints in things like, rogetactivationfactory to see a little bit of what's going on behind the scenes in winrt. something that is not obvious to me about the ipackagedebugsettings.enabledebugging api, i'm not sure if you can specify the parameters. when i specify a debugger, it seems to add the parameters "-p (pid) -t (tid)", and i'd like to know if i can tell it to provide those in a different way. with rad studio, the command line argument to attach to a debugger is "bds.exe -attach:(pid);(tid)" and in order to parse the "-p (pid) -t (tid)" i need a helper script/program. by the way, the windows 8 developer preview with developer tools english, 64-bit (x64) provides x86 and x64 debuggers, somewhat unsurprisingly at the path "c:\program files (x86)\windows kits\8.0\debuggers". automating the startup i'm still missing a part of automating my application startup for debugging, and that's actually launching the application. i found an article by raffaele rialdi on contracts and activation where he describes how explorer launches a process: "explorer uses the rpcss (rpc system service) to activate the application. as rpcss is exposed to the network and has a large attack surface, rpcss runs with low privileges (network_service) and with a integrity level system that prevents other processes with a lower integrity level can affect rpcss in reading or writing. as we have been told during the build conference, rpcss maintains the list of activated objects, and can create a pool of objects (anyone remember com+?) via iobjectcontrol. to start the process (real or surrogate), rpcss service uses "dcom launcher" that has higher privileges (localsystem). the "dcom launcher" service reads from the registry the informations related to the class and the host process and finally create the application process." this all seems like relevant and useful information, i'm just unsure how to do that from my own application. or possibly there's some way i can tell explorer to do all that? debugger woes before i mentioned attaching my application to rad studio for debugging, which is unfortunately something i've hit a bit of a road block with. i actually have the same problem if i debug with the x86 version of cdb.exe or windbg.exe. the debugger will attach fine, but when i attempt to run, i occasionally see an access violation that the application can't recover from. the access violation happens in the loader before my exe has even been loaded, so i suspect this has something to do with new linker features for win8 in cl.exe and csc.exe; there's probably some information i'm supposed to add to my exe file that the delphi compier can't do yet. oddly enough, if i attach with the x64 version of cdb.exe (or windbg.exe), i still hit the access violation, but the debugger more gracefully handles it and the application continues to load and run. i can even detach from that debugger, re-attach with rad studio, and debug my code in a more familiar environment. unfortunately, for some reason the loader loads the executable image with the name "image(randombaseaddress)" and it doesn't actually load symbols. i can force rad studio to load the symbols by opening the modules tab (ctrl+alt+m), right clicking my module selecting "reload symbol table..." and selecting my the executable or its tds file on disk. it's very clumsy, but for now, it works. posted by at 4:00 pm 234 comments: labels: appx , debugging , delphi , metro , windows 8 , winrt wednesday, december 21, 2011 directx applications in winrt windows 8 metro style apps can either use xaml as i discussed before, or they can use directx. this is great for delphi because our in our newest framework firemonkey the canvas is powered by directx on windows platforms. so once we can create a directx, we should be able to turn that into a firemonkey canvas, and the full power of firemonkey should be available to the metro style application. let's look at what visual studio generates when you specify a new directx application, and try to recreate that with delphi. earlier i looked into creating an application using windows.ui.xaml. application, but in order to use directx, you must activate the lower level windows.applicationmodel.core.coreapplication class, and construct your graphics device and surface from the ground up. as an aside, internally, the xaml application has a coreapplication as well. at //build/, matt merry gave a talk on windows runtime internals: understanding "hello world" where he shows the internals of a simple hello world xaml application, debugging down to the coreapplication level. this is a must watch talk if you want to truly understand the inner workings of a winrt application. back to delphi. like my first post about xaml, this is all pretty rough and i don't think the code is ready to share as a complete project. but i'll discuss the finer points of most of it. procedure main; var insp: iinspectable; factory: tviewproviderfactory; begin set8087cw($133f); // because we're using directx, disable all fpu exceptions factory := tviewproviderfactory.create; olecheck(rogetactivationfactory(twindowsstring(scoreapplication), icoreapplicationinitialization, insp)); (insp as icoreapplicationinitialization).run(factory); end; there's a bit of a difference here between the xaml application and this one. here, we're accessing icoreapplicationinitialization from windows.applicationmodel.core.coreapplication. icoreapplicationinitialization represents a set of static methods that is available for this class -- there is no instance of the coreapplication object. instead, we just need to provide the coreapplication class with a iviewproviderfactory which knows how to create a runnable view. my implementation of iviewproviderfactory is simple: type tviewproviderfactory = class(tinspectableobject, iviewproviderfactory) function createviewprovider: iviewprovider; safecall; end; { tviewproviderfactory } function tviewproviderfactory.createviewprovider: iviewprovider; begin result := tviewprovider.create as iviewprovider; end; the viewprovider is also pretty boilerplate: type tactivationentrypoint = ( unknown, directxapplication ); tviewprovider = class(tinspectableobject, iviewprovider) private fwindow: icorewindow; fview: icoreapplicationview; factivationpoint: tactivationentrypoint; public procedure initialize(window: icorewindow; applicationview: icoreapplicationview); safecall; procedure load(entrypoint: hstring); safecall; procedure run; safecall; procedure uninitialize; safecall; end; procedure tviewprovi

URL analysis for thomgerdes.com

http://www.thomgerdes.com/2011/12/debugging-metro-style-applications.html#comment-form
http://www.thomgerdes.com/2011/12/winrt-internals-winmd-files.html
http://www.thomgerdes.com/2011/12/writing-hello-world-for-winrt-in-delphi.html
http://www.thomgerdes.com/2011/12/directx-applications-in-winrt.html#comment-form
http://www.thomgerdes.com/2011/12/creating-appx-package.html
http://www.thomgerdes.com/search/label/metro
http://www.thomgerdes.com/2011/04/
http://www.thomgerdes.com/2011/12/hello-world-hooking-events.html#comment-form
http://www.thomgerdes.com/2011/04/hello-world.html
http://www.thomgerdes.com/2011/12/writing-hello-world-for-winrt-in-delphi.html#comment-form
http://www.thomgerdes.com/2011/12/
http://www.thomgerdes.com/search/label/appx
http://www.thomgerdes.com/2011/12/directx-applications-in-winrt.html
http://www.thomgerdes.com/2011/12/hello-world-hooking-events.html
http://www.thomgerdes.com/feeds/posts/default
interact-sw.co.uk

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain Name: THOMGERDES.COM
Registry Domain ID: 1538808944_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.enom.com
Registrar URL: http://www.enom.com
Updated Date: 2019-01-16T11:36:56Z
Creation Date: 2009-01-23T03:35:01Z
Registry Expiry Date: 2020-01-23T03:35:01Z
Registrar: eNom, LLC
Registrar IANA ID: 48
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: DNS1.NAME-SERVICES.COM
Name Server: DNS2.NAME-SERVICES.COM
Name Server: DNS3.NAME-SERVICES.COM
Name Server: DNS4.NAME-SERVICES.COM
Name Server: DNS5.NAME-SERVICES.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2019-02-09T16:38:53Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

  REGISTRAR eNom, LLC

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =thomgerdes.com

  PORT 43

  TYPE domain

DOMAIN

  NAME thomgerdes.com

  CHANGED 2019-01-16

  CREATED 2009-01-23

STATUS
clientTransferProhibited https://icann.org/epp#clientTransferProhibited

NSERVER

  DNS1.NAME-SERVICES.COM 98.124.243.1

  DNS2.NAME-SERVICES.COM 64.98.151.1

  DNS3.NAME-SERVICES.COM 98.124.243.2

  DNS4.NAME-SERVICES.COM 64.98.151.2

  DNS5.NAME-SERVICES.COM 98.124.243.3

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .