You do realize references aren't magic, right? They're a REFERENCE. Referencing a DLL doesn't magically include that DLL or its code in any fashion. Anything REFERRING to something in System.Web still needs a REFERENCE to System.Web.
∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Wed, Sep 23, 2009 at 10:46 AM, BlueVista <[email protected]> wrote: > > I followed this link to create wrapper so my client dont have to add > "System.Web.Services" and dont have to deal with webservice. The Class > Library should act like normal and should not give any hint to the > client that it's tie to a Secured Web Services (https). So far ZERO > luck. > > http://social.msdn.microsoft.com/Forums/en-US/asmxandxml/thread/ecb63966-eda7-4cfb-b417-2328b3a1abed > > I still have to add a "system.web.services" to my client reference. > Hmm any idea? >
