Epic Visual Studios "No Code"
-
On occasion, a build doesn't go quite right for some reason and the final .EXE isn't updated. I haven't seen that problem since the VS2005 days. The solution to the problem is easy: Build menu -> Clean Solution then Build your solution again and run it.
A guide to posting questions on CodeProject[^]
Dave KreskowiakI've only seen that when C# is involved. It makes copies of all the using DLLs. So if DLLs use DLLs, and there are 100 projects in the solution, you could end up with 100 copies of the same DLL. The problem then is if you change one of the DLLs. It sometimes doesn't get re-copied and the whole build falls over in a heap. I've got scripts just going round deleting all copies the DLL I am rebuilding.
-
We call them ghosts in the machine... ;P
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
Lmao, Ghosts is about right. This had me going for weeks. I just thought it would be something interesting to post and see what encounters other people have had. I seem to find all sorts of bugs with computers and Visual Studios though. The other day my computer told me it couldn't find an operating system, then I restarted it and it worked fine. I thought maybe a good line of work would be penetration testing, considering I'm good at finding bugs, and loopholes. :laugh:
<img src="http://i1125.photobucket.com/albums/l600/RainDancerSpecial/d2263f17-1c2a-453b-b3f7-8391ef2b3fb7.jpg" border="0" alt=" photo d2263f17-1c2a-453b-b3f7-8391ef2b3fb7.jpg"/> Don't Hide From The Storm, Dance In The Rain
-
I've only seen that when C# is involved. It makes copies of all the using DLLs. So if DLLs use DLLs, and there are 100 projects in the solution, you could end up with 100 copies of the same DLL. The problem then is if you change one of the DLLs. It sometimes doesn't get re-copied and the whole build falls over in a heap. I've got scripts just going round deleting all copies the DLL I am rebuilding.
All I've ever done is make the external .DLL's part of the project and mark them "Copy Always". If there was a problem, Clean always worked. I never had to build a special script to do any of this for me.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak -
Has anyone else come across the bug in Visual Studios 2012 where it runs code that isn't there? I created an application and then I decided against some of the features I had in the application. So, I removed them. Buttons and grids etc. were removed, but alas, Visual Studio 2012 is so epic, it still ran all the missing code and displayed everything I removed. I went further into this and decided to start from scratch, deleted the entire application and started a new one with the same name. It obviously didn't delete the previous project code completely, and had it stored somewhere, after it had deleted the actual project, so when I finished creating the new application, it ran like the old one. FML. So I removed EVERYTHING, all code, and the entire GUI and it still ran. WTF? I eventually copied the code, pasted it in notepad, and started in a blank app instead of Windows forms. Pasted the code back and added everything else manually.
<img src="http://i1125.photobucket.com/albums/l600/RainDancerSpecial/d2263f17-1c2a-453b-b3f7-8391ef2b3fb7.jpg" border="0" alt=" photo d2263f17-1c2a-453b-b3f7-8391ef2b3fb7.jpg"/> Don't Hide From The Storm, Dance In The Rain
If you have two or more projects open, for copying, there could be a memory leak if both have been debugged. You are probably not notified of orphaned files when recreating a project. When copying a backup project to replace a project in another location you would be asked whether to overwrite files. This would be the easiest way to remove orphaned files; by deleting the project again. These files would not be visible in explorer if the project were deleted but an explorer search for the project would probably find the orphaned file. Unless you are certain of how to deal with dependent files such as interfaces it is best not to rename, but recreate.
-
Has anyone else come across the bug in Visual Studios 2012 where it runs code that isn't there? I created an application and then I decided against some of the features I had in the application. So, I removed them. Buttons and grids etc. were removed, but alas, Visual Studio 2012 is so epic, it still ran all the missing code and displayed everything I removed. I went further into this and decided to start from scratch, deleted the entire application and started a new one with the same name. It obviously didn't delete the previous project code completely, and had it stored somewhere, after it had deleted the actual project, so when I finished creating the new application, it ran like the old one. FML. So I removed EVERYTHING, all code, and the entire GUI and it still ran. WTF? I eventually copied the code, pasted it in notepad, and started in a blank app instead of Windows forms. Pasted the code back and added everything else manually.
<img src="http://i1125.photobucket.com/albums/l600/RainDancerSpecial/d2263f17-1c2a-453b-b3f7-8391ef2b3fb7.jpg" border="0" alt=" photo d2263f17-1c2a-453b-b3f7-8391ef2b3fb7.jpg"/> Don't Hide From The Storm, Dance In The Rain
"Has anyone else come across the bug in Visual Studios 2012 where it runs code that isn't there?" Ok, with just that statement alone, this had to be said: I assume you're not referring to the MS bug in general where others tend to inject hacks into your system and run code that neither you, nor any other legitimate vendor, wrote. :laugh:
