c# - Should I put my billing module in it's own class library? -


i'm working on enterprise system built on framework. when got ownership of application, decide build new customer framework , transfer entire system module module without breaking entire application.

in new framework have business, value object, , data access layers; contain framework related classes. billing module has been sitting in old framework, want improve on , move it.

the question move new existing business, value object, , data access layers in new framework or give billing module different class library of it's own, while reference framework dlls? please pros , cons welcomed.

if think can usefull in other application , better build different dll billing module. advantage of not need write code again the other application.

note : here other application may wcf service, desktop app, web app etc. can utilize billing module.


Comments

Popular posts from this blog

c++ - Is it possible to compile a VST on linux? -

java - Output of Eclipse is rubbish -

jquery - Confused with JSON data and normal data in Django ajax request -