[AccessD] LightSwitch (was: Automating web page entry (was: Scrollbutton))

Hi Shamil

I feel that what you are asking for here is beyond the scope of LightSwitch. POCO and unit testing seem not to be incorporated or considered.
By the way, I located a good explanation on POCO (Plain Old CLR Object) here:
http://blogs.msdn.com/b/jkowalski/archive/2008/09/09/persistence-ignorance-poco-adapter-for-entity-framework-v1.aspx 

Please read my post to JC about the data storage.
I can't answer your other questions - I'm still working my way through the tutorials in my little spare-time ... so later maybe!

/gustav 


>>> shamil at smsconsulting.spb.ru 12-09-2010 00:37 >>>
Hi Gustav --

Thank you for your additional notes.

What about "Model First" approach?
Does VSLS allows to use it in this Beta version?
I mean to define my business conceptual model as a set of POCOs?
A set of POCOs with some sample/test data hardcoded/stored in/loaded from
plain text/delimited/xml/... files to not be "bound to" any real DBMS while
working on prototype UI and business models?
And to generate later database model from some of the classes of my POCOs
set?
Is it possible in this VSLS Beta version to keep/move all your object layer
POCOs in a (set of) class library(-ies)?
As far as I have got from VSLive presentation VSLS interacts with (EF and
WCF RIA in this Beta version?) object layer via <IQueryable> (and
obviously(?) uses .NET Reflection to get information on object layer types
etc.)

I'm not sure how then CUD operations are supported/implemented? What .NET
Framework interface is used for that? Or VSLS has got defined its own .NET
interface/API/.NET Attributes? 
They should be intensively using .NET Attribites to keep meta-information,
do they? Or they use special xml you mentioned to keep/interpret all
meta-information even on run-time?

<<<
Most data is collected in a local lsml (LightSwitchML) file but it connects
via the EF to nearly everything just like that. It is so flexible, and
validation, error messages and so on is ready at hand with zero or extremely
little code. Importantly, the EF let's you "remodel" any data source making
it very easy to adapt and connect/relate different data sources - again with
zero code; this feature alone is worth studying.
>>>
As one can guess (based on how MS usually designs development frameworks in
VS on top of .NET Framework) lsml meta-description is used on design time,
and it's used also to generate real C#/VB.NET code keeping/interpreting all
the (non generated into code) meta-information on runtime in attributes.
Yes, that should be it...

What base level VS project type lies under VSLS project - an MS SilverLight
front-end project?

Thank you.

-- Shamil

-----Original Message-----
From: accessd-bounces at databaseadvisors.com 
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Saturday, September 11, 2010 9:30 PM
To: accessd at databaseadvisors.com 
Subject: Re: [AccessD] LightSwitch (was: Automating web page entry
(was:Scrollbutton))

Hi Shamil

I understand your concern, and you are right - it is not very clever to
chose a development tool where you may get trapped.
However, as I see it, LS doesn't lock you out from any feature of Visual
Studio. C# and VB.NET are at any point no more than a click or two away and
you can create all the custom code and forms and reports you may need. 

Again, I'm convinced that the lack of true knowledge of databases is the
main trap for amateur (including most super user style) developers. For us
this trap is very distant. 
Because I feel that one of the fun parts of designing an application is
thinking out the perfect data model, I spend much time on this, and I've
seen several times that exactly doing so makes it possible to twist and
expand the application in any direction the client later may think of. Or -
putting it the other way - you have all experienced the deep breath you take
when you study an inherited application where the client asks you to make
what seems a minor modification while you can see that issues are piling up
because of initial bad design.

Thanks for link. Interesting comment indeed.

/gustav