• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

Need to hire someone

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    Originally posted by fullyautomatix View Post
    Only if Bobs code it, properly coded its actually maintainable. I just would not be able to do my work without reflection.
    Agree with that.

    If the schema designer has not thought about how schema entities map to type relationships in the code bindings, you can end up with lots of duplicated code that you can't "common up", because of a lack of common base classes in the bindings. You can get around that using reflection. I removed 75% of a code base recently by doing this. You present a type safe layer to callers, all the reflection is hidden from client code.

    I keep coming across this problem. These TIBCO experts write these schema and often they are rubbish.

    Comment

    Working...
    X