Email
Like
Liked ×
Save
Private Content
Embed
Loading embed code…
We have emailed the verification/download link to "".
Login to your email and click the link to download the file directly.

To request the link at a different email address, update it here. Close
Validation messages. Success message. Fail message.

Check your bulk/spam folders if you can't find our mail.
Loading

+ Follow

The Pain Points of C#

by Tuomas Hietanen on Jun 15, 2011

674 views

Accessibility

View text version

Upload Details

Uploaded via SlideShare as Microsoft PowerPoint

Usage Rights

File a copyright complaint

Statistics

Likes: 0
Downloads: 4
Comments: 0
Embed Views: 0
Views on SlideShare: 674
Total Views: 674

Every tier has an Interface and a concrete class Concrete class is not found easily, it may be resolved with IoC Interfaces between layers have to be constant Usually layers are “useless” pass-through-layers Maybe some null-checks (and object-mapping to another-layer-objects) OMG Ponies: http://msmvps.com/blogs/jon_skeet/archive/2009/11/02/omg-ponies-aka-humanity-epic-fail.aspx
Maintenance code changes are more expensive than development There are two main reasons to change code in maintenance: Business-need change, role change of a Domain-objectBug: Code seems to be different than how program works In any case, we have serious problems
Objects have been said to be natural model for humans. Have to be designed bottom-up (details first), although specifications are made the opposite way.
Here is a container… Then we will need manager, provider, factory, …And interfaces of course…What this actually does?
”Common” will never work, because we don’t know the future needs The only working solution for common functionality is Reflection No compile time error checking There is a reason why there is a type system in .NET!
- How hard can it be??? Noise! Basic property { get;set; } is easy. But it is hard to make objects, which someone else coulnd’t set to invalid state.
The function in the bottom is actually real… :-)
The new language and thesmaller syntax and better libraries are actually not the main point.F# also has higher level of abstraction. Like C-language has higher level of abstraction than assembly-language.
Of course, with Java, you couldn’t do anything like this:The “generics” of Java are just “syntactic sugar”, the compiler will optimize those away
- This would be ok, if the language would separate side effects in some way. However a Func can also cause a side effect. For this reason: F#-functions are not compatible with C#, Real pattern matching won’t work F# list handling has more expression power than LINQ. In addition, separating lists to different IEnumerables is hard (mostly possible only with a GroupBy-trick).
Drifting to Reflection: performance hit, loss of compiler time error checks

The Pain Points of C# Presentation Transcript

Object Oriented Programming Pain Points
Database
General Architecture(Simplified)
Data Access (O/R)
User Interface
Domain Model
User Interface
Data Model
Business Logics
User Interface Logics
Service layer
Debug
Needed Changes in Maintenance
The shape of objects have to be specified before the functionality
Object
vs. function-parameter
“Generic/common” objects
The pain points of C#
Immutable property
public class MyObject
{
    private readonly string myproperty;
    public string MyProperty {
        get{
            return myproperty;
        }
    }
    public MyObject(string prop)
    {
        myproperty = prop;
    }
}
Type Definitions
var list = new List<List<int>>{
new List<int>{1,2,3},
new List<int>{4,5,6},
};
Ok!
Noise!
Func<Func<int, List<int>, string>,
Func<int, List<int>>, int, string> S = (x, y, z)=> x(z, y(z));
F# Syntax
type MyObject(prop:string) =
member x.MyProperty = prop
let list = [[1;2;3];[4;5;6]]
let S x y z = x z (y z)
Ok!
Generics Parameter Constructor
void is not a type
There is no “either-or”-type

The Pain Points of C#

by Tuomas Hietanen on Jun 15, 2011

Accessibility

Categories

Upload Details

Usage Rights

Statistics

The Pain Points of C# Presentation Transcript