If you publish the web service and then give him only the published files he will only have the dll files and the webservice file (*.asmx) to work with.
I believe what santhosh is referring to is either doing the above or creating a second project, possibly inside the same solution. This project would be a class library project that compiles to a dll. Then in your webservice project you would only perform calls to the dll project. All that the person you give the app to would then only see the webservice code, not anything that you've extracted to the DLL. With not much information to know how you're going to pass along the web service portion of the project, I really can't be of too much help. On Apr 6, 1:29 am, sara <[email protected]> wrote: > Sorry I am fairly new to .Net. Could you please explain a littble bit > more or refer me to a tutorial or website? Thanks. > > On Apr 5, 11:50 pm, santhosh vs <[email protected]> wrote: > > > > > Why not create dll libraries and call from the service end points? > > > On Sun, Apr 5, 2009 at 10:55 PM, sara <[email protected]> wrote: > > > > Hi, > > > > I have a webservice implemented in csharp. > > > public class Service : System.Web.Services.WebService{ > > > .... > > > } > > > It consists of multiple csharp files located in a folder called > > > App_Code. I want to give this webservice to someone so that he can > > > call some of its methos but do not want him to see the source codes. > > > Is there anyway to turn the code into .exe file, dll or any format > > > other than its original csharp and then give it away? > > > > Thanks a lot, > > > Sara > > > -- > > My Web Sitehttp://everlovingyouth.googlepages.com > > My Technical Bloghttp://acutedeveloper.blogspot.com > > Skype :santhoshnta > > Orkut :everlovingyouth- Hide quoted text - > > - Show quoted text -
