having problem with .vb file corrupting.

  • Thread starter Thread starter Kevin Gabbert
  • Start date Start date
K

Kevin Gabbert

Hiya.

I'm running vb.net 2003 on a virtual machine, and I have my source
files located on the network. 256 megs virtual ram, MY machine has
1,000 megs ram.

however, when I work for a period of time, I encounter 3 problems.

#1. sometimes Visual Studio will tell me that some characters in my
files are unicode, and where would I like to save it

#2. It will tell me that the options file: myproject.suo cannot be
saved.

#3. best of all, nothing will compile, and I will be told that the
system does not have enough resources to compile my project


#1 gets quite annoying, because sometimes, I will open up my project,
I see an older version of my file, and I will find garbage at the
bottom of the .vb file.

I have noticed that if i open the same file on another machine with
Visual Studio 2003 on it, then it shows everything where it should be.
so obviously, my virtual machine must not be translating this
garbage!

anyone have a clue? this is driving me nuts!

- Kevin
 
* (e-mail address removed) (Kevin Gabbert) scripsit:
I'm running vb.net 2003 on a virtual machine, and I have my source
files located on the network. 256 megs virtual ram, MY machine has
1,000 megs ram.

however, when I work for a period of time, I encounter 3 problems.

#1. sometimes Visual Studio will tell me that some characters in my
files are unicode, and where would I like to save it

Never heard about this problem.
#2. It will tell me that the options file: myproject.suo cannot be
saved.

Mhm... I would transfer the project to the local drive using a tool like
SourceSafe.
#3. best of all, nothing will compile, and I will be told that the
system does not have enough resources to compile my project

256 MB RAM is a minimum requirement and requires you to set a very large
swap volume (1 GB).
#1 gets quite annoying, because sometimes, I will open up my project,
I see an older version of my file, and I will find garbage at the
bottom of the .vb file.

I have noticed that if i open the same file on another machine with
Visual Studio 2003 on it, then it shows everything where it should be.
so obviously, my virtual machine must not be translating this
garbage!

Maybe a problem in accessing the other drive.
 
....in the case of VMWare, I have a virtual machine on my desktop that
is mapped to the host machine. VB.net is installed on the virtual
machine. The reason I do this is to have a better version of system
restore. If my machine gets hosed by my programming genius, I simply
revert, and everything is as it was at install, just like a twilight
zone episode.

however, if I store my files on the Virtual Machine & I revert, then
piff! those files are gone. so I map to the host machine so I can
revert with impunity, leaving shortcuts to my projects on the virtual
desktop.

I notice this happens cause I hit the 'Save All' button quite a lot.
This comes from my Access days when you could corrupt the database at
the drop of a hat.

I do notice that if I delete the .suo file, then I can 'Save All'
again without issues. That is.. until it happens again. Then comes
the dreaded box that asks me if I want to save unicode characters.
Then, it is too late. I cannot even copy my existing code out of the
code sheet, because the clipboard stays empty. I get to close,
re-open, and lose all changes since some determined last-saved date.

-Kevin
 
Back
Top