Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there any way that I can prevent a designer class from being rebuilt when running my project?
The designer class is a webservice reference with over 30000 lines of code and appears to be being rebuilt almost every time I run my project. (Which obviously takes quite some time)
Is there some explicit way I can prevent Visual Studio 2010 from rebuilding this class each time I run the project?
One obvious suggestion: put it in a different project, as a class library. Visual Studio should detect that nothing in that project has changed, and avoid rebuilding it.
I realise this is somewhat ugly, but it may be a reasonably practical approach. Of course if there are other types in the project which are related to the web service and which also don’t change much, you could add them into the same project.
EDIT: While I don’t think there’s anything in the web service properties box about this, you might want to check it… and check whether the designer file itself is being regenerated. If for some reason it’s fetching the metadata on every build (do you have any custom build rules?) that would quite possibly be the problem.