aspdotnet_website_programming thread: Compile after FileManager edit
Message #1 by "Andrew Hay" <andrewh@i...> on Tue, 28 May 2002 16:36:03|
I'm unclear how an edited .cs file is recompiled after it is edited with
the FileManager module. If the .aspx file references the .cs file with a
src attribute, it will automatically be recompiled on the next request.
However, this is not the case when it is referenced with the Codebehind
attribute. What is the intended method for editing files that were
originally developed in VS.NET? BTW, I love this module!!! Killer idea!
Message #2 by "Mike Gale" <info@d...> on Wed, 29 May 2002 09:24:38 +1200|
There are some issues of fundamental approach here.
As you say there are different ways of "linking up" your code in
The VS way has merits.
1) It accommodates a three stage process from source to live site.
(Source / Staging / Live)
2) You can publish "only files needed".
3) You can run batteries of tests (on your staging site) before going
live. These tests leave you more confident that you won't get problems
on the live site.
4) You get the VS editing environment which is very productive.
The problem with altering a live site is synchronising code with your
source. I suggest that HTML or config settings (in files or databases)
may be candidates for change (on the live site) but that code isn't. (I
seldom stray from following the 3 stages, although I may publish
selectively using ftp. That way a change made on the live site can't
get lost on the next update!)
If you go with a VS (only files needed) approach then there is no
temptation to change code (it's not there) on the live site. I think
Mike Gale, Decision Engineering (NZ) Ltd.
>I'm unclear how an edited .cs file is recompiled after it is edited
>the FileManager module.