Triggering Data Changes in N-Tier
I’ve been studying n-tier architectures as of late, particularly in VB.NET with Entity Framework and/or LINQ to SQL. I understand the basic concepts, but have been wondering about best practices in regard to triggering CRUD-type operations from user input/action. So, the arcitecture looks something like the following:
Triggering Data Changes in N-Tier
I’ve been studying n-tier architectures as of late, particularly in VB.NET with Entity Framework and/or LINQ to SQL. I understand the basic concepts, but have been wondering about best practices in regard to triggering CRUD-type operations from user input/action. So, the arcitecture looks something like the following:
Event Aggregator.. not getting a response, how to determine completion?
I’m rewriting a vehicle tracking application, a google maps based thing..
Should I extract specific functionality into a function and why?
I have a large method which does 3 tasks, each of them can be extracted into a separate function. If I’ll make an additional functions for each of that tasks, will it make my code better or worse and why?
Should I add parameters to instance methods that use those instance fields as parameters?
I have an instance method that uses instance fields in its work. I can leave the method without that parameters as they’re available to me, or I can add them to the parameter list, thus making my method more “generic” and not reliable on the class. On the other hand, additional parameters will be in parameters list. Which approach is preferable and why?
A way to return multiple return values from a method: put method inside class representing return value. Is it a good design?
I need to return 2 values from a method. My approach is as follows:
Dependency injection and IOC containers in a closed project
Does it make sense to assemble my project with dependency injection containers if I am the only one who will use the code of that project?
Why is nesting or piggybacking errors within errors bad in general?
Why is nesting or piggybacking errors within errors bad in general?
What is a good design model for my new class?
I am a beginning programmer who, after trying to manage over 2000 lines of procedural php code, now has discovered the value of OOP. I have read a few books to get me up to speed on the beginning theory, but would like some advice on practical application.
Are there any specific workflows or design patterns that are commonly used to create large functional programming applications? [closed]
Closed 9 years ago.