What limitations are you running into with LightSwitch?

As with all systems of this nature, you're going to run into problems when you need to customize any of the default behaviour.

As with all systems of this nature, you're going to run into problems when you need to customize any of the default behaviour. One such example is if you try and change the way that the queries for parent -> child relationships are executed as explained in this article ayende.com/Blog/archive/2010/08/25/analy....

I think you answer is poorly worded, you are comparing "systems of this nature" to the ORM Lightswitch uses. All ORM's have their own ways of calling and very few allow control of it. – Robert MacLean Sep 9 '11 at 20:01.

LightSwitch V1 is initially targeted at non-developers, "departmental" apps etc, but they have provided many points where you can, if you want or need, drop down into code for slightly more advanced situations. You can also use just about any SilverLight control as a "custom control", or you can create your own custom SilverLight controls. You can also create custom "extensions" if you need to go even deeper.

A number of professional developers (myself included) have recognised that LS is a very handy tool to get to know & use. This interest from developers will hopefully help drive where LS heads in future versions. B2, the current version, has a Go-Live license & there are a number of us building fairly large apps right now.

There were no new features added between beta 2 and RTM (some features were tweaked though), but there has been a LOT of feedback for the team to take on board & include in V2. There's a fairly active MSDN forum, where you can ask questions & get help from users, developers, & LS team members. social.msdn.microsoft.com/Forums/en/ligh....

Considering it is in VS and you will write code trying to figure out what non-developer would cope. – Robert MacLean Sep 9 '11 at 20:03.

Biggest issue I have had is performance limitations due to the SQL queries that are generated. On large tables (> 10million records) performance isn't great, however it can be argued that the scope of Lightswitch is not for massive systems like that but rather deptmental solutions where the datasets are expected to be lower. Most of the real limitations in Lightswitch though, aren't Lightswitch issues but general Silverlight issues.

For example the limited WCF support is a problem in an enterprise app.

I have not yet run into any wall, but the customization hooks based on themes are a real pain. Also, beware that you cannot unit-test any code you add to the LightSwitch project.

1: You can definately unit test code you add! If you add it directly in sure, but you should be putting it in a seperate Silverlight compatible assembly and then adding a reference to that in your LS project and then calling that. – Robert MacLean Sep 9 '11 at 20:06 Sure, but as soon as the code needs anything related to the entities, screens, etc, you can't.

– Gustavo Cavalcanti Oct 14 '11 at 19:17 And that was exactly what I meant by "add to the LightSwitch project". What was the reason for the down vote?! – Gustavo Cavalcanti Oct 14 '11 at 19:17.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.