I think this is pretty exciting:
The BYO (bring your own) device program at one of Australia's largest insurers
means staff will be able to break free from the shackles of their
company-issued PCs and plug in their personal laptops, tablets and smartphones
into the enterprise network.
We can
..
On Tue, Mar 29, 2011 at 9:26 PM, Grant Molloy
graken...@gmail.commailto:graken...@gmail.com wrote:
Hi Joseph,
I wasn't really looking at any particular single client solution..
If Paul Stovell is listening, what did you use in Bindable Linq.. I am
downloading now to have a look, but thought you may
Of Paul Stovell
Sent: Tuesday, 29 March 2011 11:45 PM
To: ozDotNet
Subject: RE: Propagate Database changes to application
Correct, though once upon a time I did have an experiment that worked with
query notifications. From memory you attach some kind of SqlDependency object
to your SqlCommand
-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Paul Stovell
Sent: Tuesday, 29 March 2011 11:50 PM
To: ozDotNet
Subject: RE: Propagate Database changes to application
This is what I was talking about (I think):
http://msdn.microsoft.com/en-us/library/ms172133.aspx
Just to add my 2c, it's not necessarily an or choice. You could build 90% of
the app as a web app (which for webby-things, will be much faster -
Silverlight/XAML has nothing on Razor/MVC/HTML/CSS). Then if you hit something
that's difficult to do in pure HTML/JS, build that 10% in Silverlight.
+1. NotifyPropertyWeaver is the closest thing to it just works, short of the
C# team actually caring about what the language is used for beyond Fibonacci
sequence calculators in console apps.
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Chris Walsh
Hi David,
You could do a check in the finalizer of the class to see whether dispose
wasn't called, and Trace a warning or call Debugger.Break() to force the
developer to take a look.
Paul
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of David Rhys Jones
In Magellan a ViewModel has access to an INavigator service, which it can use
to navigate to other ViewModels or controllers. For example:
private void SaveCommandExecuted()
{
Navigator.NavigateMyController(c = c.Save(this));
}
The controller action might be:
public ActionResult
Re: mapping views to view models, I like to use a convention to map view models
to views (e.g., FooViewModel should expect a .xaml file named FooPage, FooView
or FooWindow). So you shouldn't have to store the mapping explicitly.
In Magellan with just MVVM it goes something like this:
1.
with ur page. So both can work with positives
and negatives either way.
If webforms was a lot more extensible, would ur argument change? The team
is actively working towards this in future design considerations.
- Paul
Sent from my iPhone
On 19/03/2010, at 4:27 PM, Paul Stovell p
, Paul Stovell p...@paulstovell.comwrote:
As a completely unrelated note, one of the original crew on WebForms
sits down the hall from me - part of me wants to walk into his office, grab
him by the collar and say 'What were you thinking?!!!'
Although I personally came to dislike the Web Forms
.
sarcasmThank goodness ASP.NET traps 'dodgy' characters like and in
user supplied data/sarcasm
--
Richard Carde
--
Paul Stovell
Stovell p...@paulstovell.com
wrote:
I think that if MVC had come out first,
Are you really trying to suggest that the MVC model was invented
*after* web forms?
--
silky
http://www.programmingbranch.com/
--
Paul Stovell
13 matches
Mail list logo
