I don't understand. Why are you making the *.wyp file read only? wyBuild respects your decision to make the file read-only (by not writing to the file).
If you want to let wyBuild save its files, then make the files read/write.
Source Control
zburnsI'm not sure there is a solution to this, but I'll ask anyway...
I'm a Visual Studio user and also use Source Control (Team Foundation).
I like to have all my files related to a project or solution under source control - just personal preference, but helps when I check out code on another machine, then everything comes with it. This makes wyBuild unhappy do to being read only.
I'd tried adding and even linking my "wyp" and "wyc" files to my project so they'll get copied over during a new build to the release folder - which works for the "wyc", but then I can't edit they "wyp" - for example if I add something else to my project, I like to update the "wyp" at the same time, so I don't forget.
Think there's a solution to this? (or a better way of doing it?)
Zack
zburnsI think Visual Studio and TFS is doing this. When something goes into source control it marks it read only and locked. It only unlocks it and checks it out (the client.wyc file) of source control if Visual Studio attempts to edit it.
I can work around it - probably better that I do. Since really it's not going to happen all that often that I change the client.wyc, etc.
Just curious if somebody else was experiencing or doing the same thing.
Zack