N
Nelson Hsu
I'd like to further discuss this thread:
"code behind problems in vs.net 2003"
http://groups.google.com/groups?hl=...ory&hl=en&lr=&ie=UTF-8&oe=UTF-8&start=20&sa=N
It seems like I can no longer reply to it so I figured I'd just put up
a new post to it.
According to Jiange Sun, you're supposed to put a page and its
codebehind file in the same directory because it's "part of a page
entity". However, how would you make sure that in a version control
system, that the graphic guys have only access to the aspx pages? If
you add your directory to a repository, when a graphic guy wants to
change the code to an aspx page, he or she will also be downloading
your codebehind pages.
"code behind problems in vs.net 2003"
http://groups.google.com/groups?hl=...ory&hl=en&lr=&ie=UTF-8&oe=UTF-8&start=20&sa=N
It seems like I can no longer reply to it so I figured I'd just put up
a new post to it.
According to Jiange Sun, you're supposed to put a page and its
codebehind file in the same directory because it's "part of a page
entity". However, how would you make sure that in a version control
system, that the graphic guys have only access to the aspx pages? If
you add your directory to a repository, when a graphic guy wants to
change the code to an aspx page, he or she will also be downloading
your codebehind pages.