i'm particularly new in developing web services. I have this existing web service i need to redo bec currently it doesnt seem to work,

The web service has a references to a DLL Class

<%@ WebService Language="C#" Class="MyClass"%>

that's the whole content...and it has a MYClass.DLL located in a bin folder

What i did is put the MYClass class inside the Web service itself....

<%@ WebService Language="C#" Class="MyClass"%>

using System;
using System.IO;
using System.Data;
//...

[System.CodeDom.Compiler.GeneratedCodeAttribute("wsdl", "2.0.50727.42")]
[System.Web.Services.WebServiceAttribute(Namespace = "http://service.search.lsc.slacker.com")]
[System.Web.Services.WebServiceBindingAttribute(Name = "TLSCSoap22Binding", Namespace = "http://service.search.lsc.slacker.com")]
public class MYClass: System.Web.Services.WebService
{
 
//...

and it did work, tested all the functions and everything worked as expected.

However, i need to see all the repercussions before proposing this solution, i might have overlooked the benefits of referencing a dll instead

Pls. note that i cannot ask the previous developer of why it was encapsulated in a DLL file and i know for a fact that this DLL will not be reusable by any other external apps. It was created solely for the web service.

So my question is why did the old developer created a dll to contain the class and be consumed by a web service, instead of just a web service?

i'm particularly new in developing web services. I have this existing web service i need to redo because currently it doesn't seem to work,

The web service has a references to a DLL Class

<%@ WebService Language="C#" Class="MyClass"%>

that's the whole content...and it has a MyClass.dll located in a bin folder

What i did is put the MyClass class inside the Web service itself....

<%@ WebService Language="C#" Class="MyClass"%>

using System;
using System.IO;
using System.Data;
//...

[GeneratedCodeAttribute("wsdl", "2.0.50727.42")]
[WebServiceAttribute(Namespace = "http://service.search.lsc.slacker.com")]
[WebServiceBindingAttribute(Name = "TLSCSoap22Binding", Namespace = "http://service.search.lsc.slacker.com")]
public class MYClass: System.Web.Services.WebService
{    
    //...
}

and it did work, tested all the functions and everything worked as expected.

However, i need to see all the repercussions before proposing this solution, i might have overlooked the benefits of referencing a dll instead

Please note that i cannot ask the previous developer of why it was encapsulated in a DLL file and i know for a fact that this DLL will not be reusable by any other external apps. It was created solely for the web service.

So my question is why did the old developer created a dll to contain the class and be consumed by a web service, instead of just a web service?