unknown problem with code

[dbarbarian]

Greetings 1st of all.
I am new to vb.net or 2008 however its called.
I created a program originally in vb5 and migrated it into 2008. It was working well after fixing some language errors. But now every time I change the code, and test the changes it doesn't test them. Keeps running in the unchanged version of that last save done.
How do I tell the system to always run the debugger/test with the code with the changes in them? I see the changes permanently on the code. But whenever I test I do not see them.

Example I put a label that says "this sucks" whenever I run it after saving it that label is not there on the testing but its there on code and design.


***** NVM found out what was happening. Every time I run a build it only runs that build even when I do changes to the code. Now its doing what's supposed to do. Thank you thou.

[techgnome]

In the future... and for anyone else that has a similar problem... if you compile and run... and your changes aren't being reflected in the run code.... clear out the bin folder...

VS runs the app by actually running it. It compiles it, in debug state to the bin/debug (assuming you haven't changed the output folders) and then runs the app, and attaches to the process. That's if you just hit F5 ... if you use Ctrl-F5... then you get a full run, no debugging... but otherwise works the same.

-tg

[dbarbarian]

Thank you. Didn't know that on VB.net. I assume that VB.net is the same as VB 2008, because most of the code I have used so far is for VB.net. I am used to do apps in VB5 long ago.

Thanks for the info on the f5 vs. ctrl-f5

[Shaggy Hiker]

VB.NET is the general name that was given to all versions of VB after VB6. It was officially the name of the language that was released as VB2002. In fact, I'm not actually sure that there ever was anything called VB2002, or if that name was given to it later to distinguish it from the other versions. This first VB.NET was followed by VB2003, VB2005, VB2008, and now VB2010. They are all VB.NET, because they are all VB, and they are all .NET. There is also a version number, much like there was VB5 and VB6, the various .NET versions also have version numbers, though they are not all that consistent. If you counted VB2002 as VB7, then VB2008 should be VB10, but it is VB9. I expect that this is because 2003 was not a full release, but I haven't cared enough to find out. Nobody refers to that version number, anyways. Just use 2008, that's good enough.

[techgnome]

generally speaking, the most important things to note is the version of VS (2003/2005/2008/2010) ... and the version of the Framework (1.0/1.1/2.0/3.0/3.5/40)

-tg