Sorry Mark, I misunderstood, and answered the wrong question to boot. I don't know what the best way is to version-control css and such. I have a shared-environment standalone setup, so I'm sure that's a bit different than what you're looking for. With my setup, if I replace css, I don't need to update app scope or anything, but then, everything is more or less in wwwroot/css, so that makes sense.
Tomek On Wed, Feb 4, 2009 at 11:19 AM, Mark Jones <[email protected]> wrote: > > I mean everything. CSS files and related images included. > > I was expecting that we would have to reload the application to accept > new types/rules, but I wasn't expecting that to cause issues beyond > the time it takes to actually reload the application. What kind of > side-effects should I expect from reloading the app scope on a > production site? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/farcry-dev?hl=en -~----------~----~----~----~------~----~------~--~---
