Question

Q:

Recently , i face some problems, i have a dll common among a lot of applications,and any change to this dll require to build it, copy and paste it in each bin folder of these applications ,and add the new reference so i decided to convert this dll to a web service in stead to overcome this overload..
I make a web service application contains set of web services(mapping to each class).

I face some problems here:

• In the original dll, there are
  classes use methods exist in other
  classes in the same dll, and i face problems when i
  tried to use web service methods in
  other web service class.how to fix
  this problem.

• In the original dll there are set of
  static classes with static
  methods.how to make the equivalent in
  my web service application.

• Any overload method cause a problem
  in my web service.

• When using Dictionary<string, string>
  as a parameter in my method.

Note:the original dll contains the connections to the data base. Is converting it to web service is the optimum solution?which one is faster in my case a web service or the dll?Should i tend to WCF instead of?

thanks in advance.

Answer 1

In my applications I usually have all related projects in the same solution. But when I need to use projects across applications I replace the project for a dll reference.

Because I use Subversion I solve the problem of copying the dll by adding an external property do my libs folder, referencing the build of the dll.

If the external dll is updated very often than you probably need a continuous integration system to handle that for you.