• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "Debgging in .Net 2003 - why does it rebuild every time?"

Collapse

  • wurzel
    replied
    Yes, that'll do the trick. Cheers

    Leave a comment:


  • ASB
    replied
    It did have a habit of doing that.....

    Can't recall the solution but what I think I did was to create a new configuration called "quickdebug" and not list anything for compilation in that config.

    No idea if this will help in your situation of course.

    Leave a comment:


  • Debgging in .Net 2003 - why does it rebuild every time?

    Hi,

    Don't know if there is a solution to this or whether it's just the nature of the beast but I have a solution containing 36 separate projects & every time I debug it insists on doing a full rebuild despite the fact that no code has changed. Is there a configuration setting to prevent this? I've looked in MSDN and have Googled but no joy.

    Thanks in advance.

Working...
X