Newbie Feedback on Framework


Author
Message
Michael Niemann
Michael Niemann
StrataFrame Beginner (29 reputation)StrataFrame Beginner (29 reputation)StrataFrame Beginner (29 reputation)StrataFrame Beginner (29 reputation)StrataFrame Beginner (29 reputation)StrataFrame Beginner (29 reputation)StrataFrame Beginner (29 reputation)StrataFrame Beginner (29 reputation)StrataFrame Beginner (29 reputation)
Group: Forum Members
Posts: 7, Visits: 73
First, let me say that I have just begun exploring StrataFrame, so some of these observations may be the result of inadequate exploration or misconception... but here goes (my background is PowerBuilder, Delphi, many RDBMS's):

I really like the web site, the examples, and the StrataFram Help (especially the Getting Started stuff). I have created a simple single form / single Business Object WinForm application... so now I am an expert. <g>

Concerns (you had to suspect this would be the longer list... right?):

1) I question the idea of binding the Business Objects right to the forms. Why not bind a BO Proxy to the forms, and keep all the BO's in one container? I know there is some ability to Share Data... but why should this be a case by case implementation detail? In fact I would see this as something you guys already already addressed (at the macro level) with the Enterprise Server alternative to the Client Server approach of connecting each BO directly to the database. IOW, why would you want each form in an application have its own (Customer) BO with a private buffer... out of synch with each other form/(Customer) BO/buffer in the application?

2) There is a loud "silence" on the WPF/SilverLight front. Along these lines, there seems to be a bit of a hush over when the next maintenance release will appear... and what will be in it.

3) The use of "Select *" in the example SQL statements. Generally we remove the fingers of developers that do stuff like that. I'm not sure how your BO's react to changes in the database tables (renaming columns, changing data types, adding/removing columns, etc.). We find explicit column references helps us find the issues pretty quickly. Along this same line is the missing ability to Auto-Generate bound controls based on a Buisiness Object (or actually BO Proxy <g>Wink.

4) There doesn't seem to be any system level caching capability.

5) Almost all the Help examples are in VB, which doesn't help a C# newbie.

6) And finally, why do the C# samples contain reverences to a VB construct...
//-- Forcibly close the application to stop message pumps from looping and preventing the application
// from closing
ProjectData.EndApp();


Reply
Ben Hayat
Ben Hayat
Advanced StrataFrame User (946 reputation)Advanced StrataFrame User (946 reputation)Advanced StrataFrame User (946 reputation)Advanced StrataFrame User (946 reputation)Advanced StrataFrame User (946 reputation)Advanced StrataFrame User (946 reputation)Advanced StrataFrame User (946 reputation)Advanced StrataFrame User (946 reputation)Advanced StrataFrame User (946 reputation)
Group: Forum Members
Posts: 374, Visits: 1.2K
2) I would not go so far as to say "silence." If you go to several of the websites of control designers in the .NET market, they all say that they are working on WPF controls, but until the design-time support is at least Beta 2 or RTM, they're not going to release them.




Hi Ben;



I had recently asked Scott Guthrie @ MS some questions about VS2008 and WPF and thought you might be interested to read his replies:



Saturday, June 30, 2007 12:09 AM by ScottGu



Hi Ben,



The Beta2 release of .NET 3.5 and VS 2008 should be fairly baked in terms of feaure set - I wouldn't expect LINQ and ASP.NET to change much after that (a few minor tweaks - but nothing substantial). So I thjink you could start then to write applications with it and not be worried about having to change much for the final release.



Hope this helps,



Scott




Monday, July 09, 2007 4:28 AM by ScottGu



Hi Ben,



VS 2008 Beta2 has support for WPF (including a built-in designer). We'll have a separate download add-in for VS 2008 that adds Silverlight support.



Silverlight will support LINQ to Objects and LINQ to XML. If you are starting a project involving data in the next 6 months, I'd definitely recommend going with ASP.NET. Silverlight doesn't yet have databinding or rich data controls built-in - which would make building a data app very tricky.



Hope this helps,



Scott


..ßen
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search