I have built a custom tool that works great, but I'm trying to see if there
is anything I can do about an annoying issue with the custom tool. If the
somefile.xml (custom tool is tied to this file) file is checked in and I run
the custom tool, then the code behind file for the custom tool gets
incremented somefile1.cs, somefile2.cs, etc... this only happens if I don't
check the somefile.xml out first. If I check out that file first and then
run the custom tool it does not increment the code behind file. Has any one
run into this issue and if so, is there anything I can do about it?
Thanks,
Eric J. Smith
Eric J. Smith - 25 Aug 2004 05:19 GMT
So I guess no one but me has run into this issue?
>I have built a custom tool that works great, but I'm trying to see if there
> is anything I can do about an annoying issue with the custom tool. If the
[quoted text clipped - 10 lines]
> Thanks,
> Eric J. Smith
ccallen - 26 Aug 2004 16:43 GMT
I have a similar code-behind problem, with a little twist (see message in
this news group "custom aspx code behind class" 8-23).
It seems like when the file is read only, it will create a new name. You
could check the files attributes for read-only, if so you could popup a
message to alert the user that the file is read only "please fix the
situation and try again".
Conan
> So I guess no one but me has run into this issue?
>
[quoted text clipped - 12 lines]
> > Thanks,
> > Eric J. Smith