vb.net project stops responding to the changes made in the code, after some debugging sessions

Question

0.00/5 (No votes)

See more:

Hi,
I develop vb.net projects, I used visual studio 2005 for one of my projects. The project seems to be in "committed " state, and does not responds to the changes made in the code. This problem starts after some 20-25 runs, during the debugging session.

Do I need to reinvent the wheel for my project?? Or is there any solution for this problem? Please Do answer, Thank you in advance.

-deveshdevil.kumar6@gmail.com

Posted 29-Oct-11 0:43am

Deveshdevil

Add a Solution

Comments

Richard MacCutchan 29-Oct-11 7:53am

what do you mean by "committed" state? Have you done a complete rebuild of your project? Does it have dependencies that need to be rebuilt?

2 solutions

Solution 1

By the term "Committed", I can assume that you may be using a version control tool like "VSS" or "Trotorise SVN" or some other tool. If so and if your code recently broke, then you can revert your recent changes (if they are not critical changes) and repeat only the recent changes again after ensuring the stability of the source.

Alternatively if the local source is only not working but the source on the reprository is stable, then you can check out (or pull the latest source) from repository to a new directory and then use some file comparison tools like "Compare It"(Google it) to compare those two and figure out the required/unwanted changes.

Hope it helps...

Thanks,
Kathir

Posted 29-Oct-11 11:06am

Kathiresanmurthy

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Nish Nishant · Accepted Answer · 2011-10-29T11:11:00

I interpreted your question to mean that changes you made to the code are not reflected when you run the application. The most common cause for this is that you have one or more DLL projects and the recent code changes are on those projects. For whatever reason Visual Studio fails to copy over the updated DLLs to the exe folder (there have been various such bugs in recent versions of VS). A quick fix is to do a clean of the solution and to make sure that the changed DLLs are indeed copied over.