We have just migrated from VS 2003 to 2005.  We use a number of web references in our ASP.NET projects.  However I have noticed that VS 2005 does not seem to generate a proxy class.  As a result I am getting CLS compliance warnings all over the shop because I use web service classes in functions and methods.  Would be grateful if someone could tell me how I should be generating my web references or if there is something else I can do to get around this issue.  I am not sure if including web service classes is bad practice but some of the web reference objects are quite complex and refactoring out the manipulation of them into functions/methods seems like a logical step.

Also the dynamic web reference property seems to have gone from web references, which allowed us to dynamically define the location of a web service in the web.config.  I am sure there is a good reason for this apparent reduction of usability and functionality, so any pointers would be greatly appreciated.