Lloyd
Sun May 11 18:52:28 CDT 2008
"ShaneO" <spcacc@optusnet.com.au> wrote in message
news:48278163$0$30463$afc38c87@news.optusnet.com.au...
> Lloyd Sheen wrote:
>>
>> "ShaneO" <spcacc@optusnet.com.au> wrote in message
>> news:48275f0b$0$1024$afc38c87@news.optusnet.com.au...
>>> John wrote:
>>>> I just say Yes to save and get on with it.
>>>>
>>>
>>> I would agree with this sentiment, just say YES.
>>>
>>>
>>>> "Lloyd Sheen" <a@b.c> wrote in message
>>>
>>>>>> I now have to go into the designer file since ToolStripStatusLabel's
>>>>>> do not really exist in the form by themselves. Re add them and wait
>>>>>> for the next time I open the form.
>>>>>>
>>> Are you therefore implying that you don't have ANY sort of Backup? No
>>> roll-back point that you can go to in order to overcome the need to
>>> modify the Designer file? Surely not!
>>>
>>> Even if you discover the problem after you've made substantial changes
>>> to your code, I believe you'll find that you can still swap-in an old
>>> Designer.vb file to recover any corruption.
>>>
>>> VS2008 is not perfect, neither is the Operating System that you're
>>> running on, or probably the CPU, Hard Disc Drive, RAM or anything else
>>> in your system - Make contingencies available for when/if something goes
>>> wrong and you'll easily recover!
>>>
>>> ShaneO
>>>
>>> There are 10 kinds of people - Those who understand Binary and those who
>>> don't.
>>
>> I have backups. I used a diff program to see what changed. NOTHING.
>>
>> I would like to know where the "extra" files are for solutions. There is
>> something in those files which causes the problem I think.
>>
>> About perfection. If you create an application would you think that by
>> simply opening a file it should be marked as changed. I don't think that
>> any customer would accept this.
>>
>> LS
> I believe you'll find that there aren't any "extra" files, so therefore
> your Diff program has obviously missed something somewhere!
>
> In the past I've been sent a ZIP file from friends containing all the
> files you'll see in any project folder. I have then performed some work
> on the project (including running it locally) and sent it back with the
> changes. My own projects are stored on a Server which I access from a
> number of workstations, and at times I have even copied the project folder
> onto a Notebook and been able to continue to work locally. If there were
> "extra" files hidden somewhere, this would not be possible.
>
> Also, if you believe there weren't any differences between your old
> Designer.vb file and the current one, what did you mean by - "I now have
> to go into the designer file"?
>
> As I've never experienced the exact problem you originally described, I am
> genuinely interested in finding out more, but I can be fairly certain you
> won't find an answer by looking for any files that aren't already clearly
> apparent.
>
> ShaneO
>
> There are 10 kinds of people - Those who understand Binary and those who
> don't.
I sure can't find easily any extra files. I have use procmon and can see no
files that would suggest they hold information about outlining etc. I have
loaded the .vb file into a hex editor and there is nothing I can see that
would indicate whether a subroutine is open or closed (outlining).
As for moving the files around I would think that you would not know the
open/closed status of any subroutine and that if the info did not exist then
all method would show as expanded in the IDE.
Going into the designer file was to add the existing statustext controls
back into the statusstrip. The original problem (other than the fact that
it will open this one form as changed each time) was that the statustext
controls exist but were somehow not added to the statusstrip (or at least
the code was somehow changed by opening the form in the IDE.)
I have also had the IDE create for me stubs (which are incorrect) for events
from a usercontrol. This does not happen if I clean the solution.
Somewhere in VS 2008 there is a problem and I would like to find it. I
often make many changes and rely on the "changed" status to ensure that
things that were to be done were done and visa versa.
LS