That may sound like a stupid question, but let me explain what I mean.
Let's say we have ASP.NET application "MyApp".
The directory structure looks like this:
MyApp\foo
MyApp\bar
MyApp\bin
Programmer A makes changes to pages in MyApp\foo.
Programmer B makes changes to pages in MyApp\bar.
Neither one has the other's code changes so we he compiles (builds) his copy of the project, the changes from the other person are not in the dll. Example:
Programmer A uploads his new files, including MyApp\bin\MyApp.dll.
Then Programmer B does the same, overlaying Programmer A's dll. Programmer A's changes get blown away.
That is the problem my buddy and I are trying to solve. How can we work independently on separate pages without needing to send our changes to each other for the "build" process?
---
Marco Barzaghi - 07 Aug 2004 13:57 GMT
> Then Programmer B does the same, overlaying Programmer A's dll. Programmer A's changes get blown away.
You can use "src" directive of @page. Look at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/c
pconPage.asp. Using
"src" you must upload the source of codebehind too.
--
Src Specifies the source file name of the code-behind class to dynamically compile when the page is
requested. You can choose to include programming logic for your page either in a code-behind class
or in a code declaration block in the .aspx file.
Note RAD designers, such as Visual Studio .NET, do not use this attribute. Instead, they
precompile code-behind classes and then use the Inherits attribute.
--
HTH M.rkino
--
Marco Barzaghi - [MVP - MCP]
http://mvp.support.microsoft.com - http://italy.mvps.org
UGIDotNet - User Group Italiano .NET, http://www.ugidotnet.org
Read my WebLog: http://www.ugidotnet.org/436.blog