Hi Greg,
You're looking at the results of a URL protocol handler. See here for more
info: http://msdn.microsoft.com/en-us/library/aa767914(v=vs.85).aspx
ciao, Richard
Aussie Bushwalking
It's like Wikipedia... but for Bushwalkers!
http://www.aussiebushwalking.com/
On Wed, Sep 21, 2011 at 1:18
On Mon, Jun 20, 2011 at 3:32 PM, Michael Lyons maill...@ittworx.com wrote:
This is very true, but in a lot of cases people could easily use REST
instead of SOAP and vice versa as they are just doing basic CRUD or workflow
operations
I agree. I was just pointing out that its unjustified to
On Mon, Jun 20, 2011 at 9:45 AM, Michael Lyons maill...@ittworx.com wrote:
REST is what SOAP should have been, but something along the way just went
wrong.
I'd strongly disagree with this. REST and SOAP have fundamentally different
design goals. If the SOAP designers came up with REST they
The Convert class will help:
value = (T)Convert.ChangeType(rawValue, typeof(T))
On Sat, Jun 4, 2011 at 10:40 AM, Greg Keogh g...@mira.net wrote:
Folks, in the tiny sample below I want to parse some text and set the
generic value, which will be int, double or long. The highlighted
statements
Or perhaps use GC.KeepAlive
On Mon, Nov 1, 2010 at 9:34 AM, David Kean david.k...@microsoft.com wrote:
If by using a local variable you mean local field, then yes this is
reliable.
*From:* ozdotnet-boun...@ozdotnet.com [mailto:
ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Greg Keogh
I think the NativeWindow class may be able to help you run a simple message
loop without any UI. Here's some quick code I threw together in LINQPad as a
proof of concept.
void Main()
{
var w = new MyWin();
w.CreateHandle(new CreateParams());
Thread.Sleep(5000);
w.DestroyHandle();
}
// Define
Having just bought an AMOLED phone I can confirm that they are definitely
nothing like the eInk. At the very least make sure you go see an eInk
device. They're an entirely different beast.
ciao, Richard
On Fri, Sep 3, 2010 at 4:21 PM, Simon Reed simon.spectre.l...@gmail.comwrote:
Can't comment
Hi Greg,
I've worked on a project which has done the scripts in source control
approach. I think the thing which made it work was that part of the CI build
was to actually spin up a new db and run all the scripts. Failure of the
scripts to run triggered a build failure and appropriate blame
Hi Michael,
You want to look at the windows power management functions, in particular I
SetThreadExecutionState. MSDN link:
http://msdn.microsoft.com/en-us/library/aa373163(v=VS.85).aspx
http://msdn.microsoft.com/en-us/library/aa373163(v=VS.85).aspxciao,
Richard
On Wed, May 5, 2010 at 10:38 AM,
