| Author |
Message |
|
David Wie
#1 / 5
|
 ? VB6 Weirdness When I make a change to a program in VB6, I always save the form, then save the project & then re-compile & save the EXE. However, when I close VB6, it always asks me if I want to save the project, so I say yes. BUT, when I use the Project & Deployment wizard, I it recognizes the project
as being newer than the EXE & asks me if I want to recompile, and, wanting
to be as safe as possible, I choose to do it.
Any ideas what's causing this?
|
| Fri, 01 Jun 2001 03:00:00 GMT |
|
 |
|
Tom
#2 / 5
|
? VB6 Weirdness Quote:
>When I make a change to a program in VB6, I always save the form, then save >the project & then re-compile & save the EXE. >However, when I close VB6, it always asks me if I want to save the project, >so I say yes. >BUT, when I use the Project & Deployment wizard, I it recognizes the
project
>as being newer than the EXE & asks me if I want to recompile, and, wanting
>to be as safe as possible, I choose to do it.
>Any ideas what's causing this?
I can answer the second part... When your compile, then save, then use the deployment wiz, it checks to see if the time/date stamp on your existing exe is older than the last save done, which if you (or VB6) save AFTER you've made an exe, it is therefore, older... WHY it wants you to save after you have just done so I'm not sure...
|
| Fri, 01 Jun 2001 03:00:00 GMT |
|
|
|
charl
#3 / 5
|
? VB6 Weirdness Tom, I am not defendig the behavior, it is definitely a quirk. But, the
reason you have to save after you compile, even if you saved right
before the compile, is for things like version number incrementing and
the like (ie compile once and the version number goes up, thus, you
have to save it to retain the new version number).
Why VB6 PDW insists on a new compile, to which I almost always respond
'No', I am not sure. It did definitely throw me the first time I saw
it though. VB5 has the same issue of auto-increment, and the Setup
Wiz. was smart enough not to prompt over and over for a recompile, or
maybe it was simply ignoring the timestamp altogether.
Regards,
Charlie
Quote:
>>When I make a change to a program in VB6, I always save the form, then save
>>the project & then re-compile & save the EXE.
>>However, when I close VB6, it always asks me if I want to save the project,
>>so I say yes.
>>BUT, when I use the Project & Deployment wizard, I it recognizes the
>project
>>as being newer than the EXE & asks me if I want to recompile, and, wanting
>>to be as safe as possible, I choose to do it.
>>Any ideas what's causing this?
>I can answer the second part... When your compile, then save, then use the
>deployment wiz, it checks to see if the time/date stamp on your existing exe
>is older than the last save done, which if you (or VB6) save AFTER you've
>made an exe, it is therefore, older... WHY it wants you to save after you
>have just done so I'm not sure...
|
| Sat, 02 Jun 2001 03:00:00 GMT |
|
|
|
Len Weav
#4 / 5
|
? VB6 Weirdness Hi Dave, Quote: >When I make a change to a program in VB6, I always save the form, then save
>the project & then re-compile & save the EXE.
>However, when I close VB6, it always asks me if I want to save the project,
>so I say yes.
If you have your project setup to 'Auto Increment' the version numbers then the App.Revision property will be incremented after a compile (in preparation for the next compile). This constitutes a change to the project file, which causes the prompt for a re-save. Hope this helps,
Len
---
Len Weaver
MeritSoft Corporation
Len DOT Weaver AT Sympatico DOT Ca
|
| Sat, 02 Jun 2001 03:00:00 GMT |
|
|
|
David Wie
#5 / 5
|
? VB6 Weirdness You're right - I have my program setup to auto-increment. But this seems like a stupid way to do it....it seems that the only time it
should increment is as it's saving the next time - not after...
But - then again - maybe that's just me.
Quote:
>Hi Dave, >>When I make a change to a program in VB6, I always save the form, then
save
>>the project & then re-compile & save the EXE.
>>However, when I close VB6, it always asks me if I want to save the
project,
>>so I say yes.
> If you have your project setup to 'Auto Increment' the version numbers
>then the App.Revision property will be incremented after a compile (in
>preparation for the next compile). This constitutes a change to the
>project file, which causes the prompt for a re-save.
>Hope this helps,
>Len
>---
>Len Weaver
>MeritSoft Corporation
>Len DOT Weaver AT Sympatico DOT Ca
|
| Sat, 02 Jun 2001 03:00:00 GMT |
|
| |
|
