Visual Basic Express project is not (always) saved on disk - vb.net

I'm a Visual Basic newbie, doing a quick'n'dirty VB app in Visual Studio 2010 Express (under Windows 7, 64-bit).
I save constantly. I have used the "Save All" option. I have rebuilt the app.
Still, the project is not always written to disk when I save! (sometimes, my changes are written to disk, but I haven't found out yet the pattern). This is really bugging me, since quite a few times I saved my project, closed VB, and then I realized all my changes had not been saved.
Is this some limitation of VB Express? I am using Visual C++ Express, too, and I had no such problems there.
EDIT: For even more clarification -- I am not getting any errors, and I am not having problems with version control. What I do is:
I make changes in source file.
I press save.
I rebuild, at a certain time hh:mm.
I look on the disk, and sometimes my source file's "last modified time" is not hh:mm, and if I open it, the changes from 1) are not in the source file. Sometimes it is there, but I can't say for sure when or why.
The config on my machine is nothing special as far as I know, just normal Windows 7, 64-bit. I guess if it were some access rights related issue, the saving would never happen, instead of what I'm experiencing now.
By now, I think one can safely assume that this is no Visual Studio Express issue (just installed it as it came, using it "out of the box").

Related

VB.Net Windows Application requires rebuild every time even for small changes

I have created windows application in VB.Net 2010. The problem is that even for a small change, I have to rebuild the project. Without rebuilding it, the changes do not take place. What may be the problem or something else?

There is no problem here. That's the way it's supposed to work. Unlike vbscript and vba, which were interpretted, VB.Net is a compiled language.

Adding line breaks when editing .vb files in Visual Studio 2010 very slow

I'm using Visual Studio 2010 with SP1 installed.
I'm experiencing a huge lag of between 0.5 to 2.0 seconds every time I either enter a line break or remove a line, but only when editing VB.NET files (extension .vb).
Oddly, 'normal' typing on just a single line (along with Intellisense) is still very responsive.
Has anyone got any tips or clues as to how I can speed this up? My google-fu is letting me down.
The machine specs are fairly healthy, and the issue is not prevalent when editing any other filetype inside Visual Studio (c# etc).
Edit: Just as an update, all addons and extensions are disabled.

Visual studio Project creation issue

Ok bear with me because i am frustrated beyond belief right now.
go back about 30 minutes ago, i create a VB windows forms application. cool, nothing out of the ordinary only i make a big mistake and decide to start again. so i close the solution, delete the project folder and go to start again, only now i'm presented with
"requested operation cant be performed on file with user-mapped section open"
ok i think, there's obviously something still reading it or whatever, so i close VS completely and restart.. no avail. log off and try again. nothing. restart the computer. still nothing. what is causing this issue? i can create a C# Windows Forms Application without a frigging problem. everything BUT a VB WFA. what do i do? i'm in no real position to re-install VS right now or i'd have started 20 minutes ago. i really need a helping hand here please

Visual Studio keeps changing resx files

I'm working on a VB.Net project and using SVN. I noticed that every time I open my main form, Visual studio slightly modifies my .resx file, which means that I keep having to re-commit it, which is quite annoying.
Has anybody experienced such problems? A diff file demonstrating the problem can be seen at http://synchronicity.svn.sourceforge.net/viewvc/synchronicity/trunk/Create%20Synchronicity/MainForm.resx?r1=272&r2=359&pathrev=359
Thanks,
CFP.

Bit late, but this sounds like a problem I raised with Microsoft around Image Lists:https://connect.microsoft.com/VisualStudio/feedback/details/428868/png-files-corrupted-in-an-imagelist-when-opening-and-closing-a-form

What can cause Visual Studio 2008 to hang while debugging?

I have a vb.net project which sometimes, when running in the IDE, suddenly hangs. Normally this wouldn't be a problem. Just hit 'pause', look at the currently running threads, and find the deadlock (or whatever else).
But now I'm running into a situation where not only does the program hang, but trying to pause it causes visual studio itself to hang. In order to get control back, I have to kill the program-being-debugged's process, at which point visual studio comes back to life and says it was unable to pause execution. This is frustrating, because killing the process means the program state is lost (of course), so I don't know where the hang is.
So are there any common causes for this behavior? What should I be looking for?

if your program installs global hooks (which communicate with app) - this might be the case. A hook tries to communicate with your app (which is paused by debugger) and gets locked. And debugger is unable to receive its window messages: classic deadlock between hooked debugger (with hook dll) and a hooking app.

Finding a specific fix for a Visual Studio problem can be tricky: http://social.msdn.microsoft.com/Search/en-US/?query=visual%20studio%202008%20hang&ac=3
Additionally, not all hotfixes from Microsoft get released directly to the public. Some are only given out to customers whose systems are exhibiting a specific problem. So you have to contact Microsoft to the get the fix. They do this to limit the potential downside of releasing a hotfix that may break something else. So if all else fails, give them a call.
Here are some other things that I like to do when Visual Studio starts acting up:
Delete old breakpoints and watch variables.
With visual studio not running, delete the intellisense file (.ncb)
Clean the solution and then do a rebuild of all of the code.

Check hotfixes and service packs. I've seen a bug related to .net programming and debugging hangs. (VS hangs for me when debugging C++ 32-bit apps on 64-bit os:es sometimes.)

I just had a very similiar issue (VS fails to break execution), using Debug -> Delete all breakpoints solved the issue.

I'd check the code of the program being debugged, I'm thinking there may be an infinite loop or race condition in the code you're trying to debug. This has been the case for me in the past, especially on a single-core laptop I used to have. Can you give any information about where in the program you think execution is when you try to pause?