Note that there are some explanatory texts on larger screens.

plurals
  1. POLiving on the edge: can I change a constant string in a deployed asp.net website page dll?
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COIf you've got access to the DLL to be able to make changes to it, why can't you just republish? If it's just procedure, can't you explain it's safer to republish than to attempt a hacky fix with potentially unknown consequence? In a way, isn't changing the DLL just republishing it anyway, in a manner of speaking?
      singulars
    2. COI'm going to have to agree with bgs264 on this one. (I know, I read your disclaimer at the start of the question.) Editing the DLL, from the perspective of the runtime, is no different from replacing it. The file is changed, it has to be re-loaded. (Someone like Jon Skeet may be able to shed more light on the internals of that.) Re-building the DLL properly and swapping it out is safer and accomplishes, from the perspective of the runtime, the same thing.
      singulars
    3. CO@David / @bgs264: I agree, but the pages have not been published with single-page assemblies and/or strong naming, thus just replacing will not work. Yes, changing *anything* in the bin directory will reload the web site. But our application deployment is a bit more involved than just that, and having the website shortly on hold while reloading (takes 1 minute) is better than having a maintenance screen on the website (takes typically an hour and can only be done Sunday's, 4AM).
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload