Hi all,
I use to copy examples to study and change them.
If I change name of prohect (doing a SaveAs) I obtain a new wbs file as expected but if I deploy it (by copying in another folder) I find in 2 couples of identical files deployed.
The first couple has right name (<new project name>.html and <new project name>.js) and the second has older name (<old project name>.html and <old project name>.js) .
If I do another Project / SaveAs with another name, deployed files are 6 and so on.
It isn't a locking problem but an annoying one.
Is a bug or do I do something wrong?

Many thanks in advance

Bill wrote:

> identical files deployed

The deployment only ever copies the relevant files to the destination.
It doesn't clear anything out, as you may have other valuable content
there that is unrelated to your project. Just delete the files you
don't want any more.

--

Matthew Jones

> identical files deployed

The deployment only ever copies the relevant files to the destination.
It doesn't clear anything out, as you may have other valuable content
there that is unrelated to your project. Just delete the files you
don't want any more.
>
>
Sorry to bother all, but behaviour I saw is different.
In fact, I clear manually the deploy folder BUT, at next deploy, deployed files are two for each project rename.
So it seems like a incremental file production.
As sayed, for instance, if I rename the EWB project for two times, I'll expect that produced files are only 2 (ProjectName.html and ProjectName.js) .
In the deploy folder (cleared before deploy action in the IDE) I'll find 6 files (ProjectName.html and ProjectName.js, ProjectName2.html and ProjectName2.js and, finally, ProjectName3.html and ProjectName3.js).
It's sayed by the popup on the IDE too: "6 files copied".
It could be a bug?

Are the files in the output folder? Clear that first.


--

Matthew Jones

<< It could be a bug? >>

No, as Matthew indicates, the deployment just copies whatever is in the output folder, so you'll need to make sure to delete anything there that you don't need anymore, if you don't want it copied to the deployment destination.

Tim Young
Elevate Software
www.elevatesoft.com

> No, as Matthew indicates, the deployment just copies whatever is in the output folder, so you'll need to make sure to delete anything there that you don't need anymore, if you don't want it copied to the deployment destination.
====
Many thanks!
Now I understand clearly that he talk about source output folder and not about deployed folder.
It's working!