WDI, I'm responding to your e-mail back in the forum. WDI wrote: Hi this is exact problem. when i add webmethod to webservice and build it and update client webreference, client knows the new webmethod without any problem. but when i add a new class to webservice project and build it and update client webreference, client doesnt know the new class. Note:this is a new problem and a few days ago when i added a new class to webservice client could knows new class. this problem is for new solutions too. If you added a new web service class by putting it into a new ASMX file, then that's a separate web reference. You'll need to add it to the client project as a new web reference. If you added a new web service class to the existing ASMX file, then it won't be visible to the world. You can only have one web service class in each ASMX file. Your project will still build if you do this, but only the first class will be exposed in the WSDL. Hope this helps, PatrickShane

ImanMahmoud wrote: Threading is not a solution because the 4 blocks must be performed orederly, the 1st is performed and saved then the second, and so on. You misunderstand me. I didn't mean you need a separate thread for each block of work. I mean you need to move the these 4 blocks of work onto a background thread to get them off the thread that services your WinForm. You can do all 4 blocks in the same background thread in the same order that they're done now. If you leave the long-running work in the main thread, then your application will appear to "hang" to the end user while this work is being performed. Your application won't be able to repaint itself, it won't respond to their mouse clicks, etc. You're setting yourself up for a bad user experience this way. Seriously, go read that 2 part article I gave you a link to. ImanMahmoud wrote: My application hangs due to overload, because it performe a task then save it the read from what it saved to perfrome the following task the save it, and so on. How did you reach the conclusion that you're hanging due to some mysterious "overload" problem? If the code runs correctly in the Visual Studio debugger with the same data you're using when you run it outside of the debugger, then it's highly unlikely that your app is hanging for the reasons you suspect. Do you have PerfMon data to show whether this is a high-CPU-usage hang or a low-CPU-usage hang? Are you calling any of the classes you use from the .Net Framework asynchronously? Have you put any tracing into your code so that you can tell what point your code gets to when the "hang" occurs? Do you have any exception handling in your code? If so, are you swallowing errors that might give you a clue what the problem is? Have you examined your code for infinite loop issues? If you're using large amounts of memory in these 4 blocks of code, then it's possible (but not likely) that .Net garbage collection is running and blocking your app. If that were the issue, then it could appear to you that your application is "hung", but it wouldn't stay in that state forever. Your code would eventually resume. Looking at a "hang" dump of your app's process would be the only way to confirm this. If you've tried everything else that you can think of to determine the source of the "hang", you can always download the Debugging Tools for Windows and use them to take a series of hang dumps of your application. You can then open the hang

WDI, If you are modifying the web service project that you've added a web reference to, then you can make VS update Reference.cs by right-clicking the web reference and choosing the update option. You'll need to rebuild and/or re-deploy the web service after you change it and before you do this, of course. If you're writing a designer for a custom control, then give us some more details because I'm not sure what you're trying to accomplish or what the problem is. PatrickShane Microsoft Web Services Team

It sounds like you probably have a number of performance issues going on here, but let's focus on the obvious. First, your app freezes when the button is clicked because it's single-threaded. You should queue a user work item or spawn a new thread to do the long-running work in the background. Check out this two-part article from Visual Studio Magazine. It covers exactly this topic. http://www.ftponline.com/vsm/2004\_06/magazine/features/jberes Second, you say your program "stops" halfway through. Does "stop" mean it crashes or does it mean it hangs or does it mean it just seemingly mysteriously doesn't do what you expect? Run your code with the Visual Studio debugger and step through it to find the problem. Check the documentation for Visual Studio if you need help with this. Hope this helps