Click here to Skip to main content
15,880,972 members
Please Sign up or sign in to vote.
2.50/5 (2 votes)
See more:
Please, I need help with visual studio. Because of hard disk space run-out, I copied my projects into an external hard disk and execute them there, but I can't understant why changes I make to the projects are no longer recognised and effected. No matter what code I write, the visual studio keeps loading the version compiled much previously. For, instance, if I enable a radio button by writing some code(i.e. EnableWindow function) visual studio doesn't effect the new change. Please, how can I correct this problem?Actually, I am writing a windows program using native C++.


One other problem I faced is that intellisence was not working in debug mode. It works only WinMain but not in the main window or dialogue procedure. What could be wrong?
Posted
Updated 5-Jun-12 6:30am
v2

When moving project around, it is best that you delete all temporary files (exe, object files, ... ) and completely rebuild everything.
 
Share this answer
 
Comments
Sergey Alexandrovich Kryukov 28-Jun-12 15:38pm    
Yes! My 5. And it's important to know exactly what is the source and what is not. So many developers post all those *.suo, *.user obj/*, etc. (And some even miss important files like those generated by the designer but actually presenting programming artifacts.) Too bad Visual Studio does not help much to make a clear distinction.
--SA
Clifford Nelson 28-Jun-12 17:04pm    
My 5 also. That is also true when publishing to CodeProject. Even get rid of the Solution file if it is a single project solution.
One thing you can do is open the solution file in explorer, and then search for "bin". Delete all the folders named "bin". Now search for "obj" and delete all the folders named "obj". What can happen is that you end up with stuff in these folders that is old, and never get deleted as you recompile.

Also, check for any image files. These can be massive, and they are copied when you compile the project. Going with simpler images may help.
 
Share this answer
 
Comments
Gbenbam 8-Jun-12 14:50pm    
Thanks. I deted all obj files for debug an release and the problem was solved. As a rule now I delete all obj. files before copying projects
Clifford Nelson 8-Jun-12 15:03pm    
DO up vote. Whenever I upload to CodeProject I remove the bin, object, snd for single project solutions, the solution files. I have had problems in the past where things work because I have old dll's in the bin folder, and somebody else cannot run out of source control. Good idea to delete these files sometimes to make sure you are not running because of legacy files.
Sergey Alexandrovich Kryukov 28-Jun-12 15:39pm    
Sure, a 5. Please also see the Solution 1 and my comment.
--SA
Clifford Nelson 28-Jun-12 17:34pm    
I totoally agree. One of the issues I have with Visual Studio is that sometimes something builds on one machine but not another because of things left in the bin folder.
Aside from the recommendation from Maximilien, are you sure you're opening the correct solution file? Maybe you're still opening the old one, I don't see how Studio could be doing this at all unless the files you're changing aren't even associated with the solution you're looking at in Studio. In VS2008 you even get warnings when a file has been changed outside of the IDE so that you have the option to reload the file.
 
Share this answer
 
I had that problem before, I had to build the project to reflect changes (Run didn´t build).

Go to the solution, properties, "Configuration Properties", "Configuration".
Check the "Build" checkbox for the project (both Debug and Release).

Hope it helps.
 
Share this answer
 

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



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900