I am thinking of building a code base for my company - by catching libraries, sections etc. employees, on internal and timely The code used in different applications will be reusable in the objective time. The platform I target is only the net. - WinForms, WPF, Web, Silverlight, and others. I was thinking of building a solution that would have 2 projects for each technique - 1 in which the code occurs, and the second would be in the form of a test site for that code. What would be the best solution to handle all the different techniques and codes, what do you think?
You can imagine as much harder as you can do in this kind of company What kind of work do you have, and depends on the scope of your ambition, in large part.
First of all, you probably do not want to create "framework." You already have the .NET Framework.You may want to agree on the general set of custom controls. I'm discouraging you from trying to write your own custom controls which will be reused in many projects, developing a consistent and consistent custom control library is a big task, and
I have seen a consultation company (which was usually a custom .NET business application for customers) working again for any other project. : Try to use it, and most of it was not beautiful, take the code that was written and used in a custom application and it seems to move it to another custom application. Is more difficult Lna. It is very difficult to remove all often, code "makes assumptions about normal" piece of the overall application, or it depends on the degree of application-specific code and the dependence.
Now, if you are working in an environment where everyone is working on programs that process the same type of data, you can probably take advantage of a normal group of data access and reporting modules , And some common algorithms. Be careful here, though. Any share code should have as much dependence as possible Otherwise, potential customers (i.e. other programmers) would prefer to roll themselves instead of "Include the world".
You say that you want to create a code base in which "libraries, classes etc. should be developed." Used internally by employees and on time in various applications. "It is for me to say that you want to share codes between uneven projects, or at least take codes that were written for a project and it was used in another. It is a laudable goal, but Often difficult. As I have indicated above, there is a big difference between the writing code that works for a single project, and is writing the code which, with minimal dependence, many projects The Wara can be used. Possible, but difficult and time consuming.
Comments
Post a Comment