F
Frankie
I have a bunch of ASP.NET Web sites on a production server. Until today,
some had the aspnet_client folder and some did not. I just ran
aspnet_regiis -i as part of a troubleshooting effort and suddenly ALL of the
ASP.NET Web sites have the aspnet_client folder (and its sub folders).
The sites that previously did not have the aspnet_client folder seemed to
work just fine (for a long time). The sites that previously had that
folder - well, I don't know why they had it. All sites seem to still work
fine with it (now that they all have it).
So - can I get rid of it? I don't like to clutter production servers with
unnecessary stuff where I can obviously keep it clean. If it's unnecessary
can I just delete it from all production sites, or is it part of some larger
set of operations that aspnet_regiis -i did that I'd also need to reverse? I
don't do any development on this production server (no need to connect with
VS.NET, FWIW), and no FrontPage Server Extensions are required on this box.
Thanks!
some had the aspnet_client folder and some did not. I just ran
aspnet_regiis -i as part of a troubleshooting effort and suddenly ALL of the
ASP.NET Web sites have the aspnet_client folder (and its sub folders).
The sites that previously did not have the aspnet_client folder seemed to
work just fine (for a long time). The sites that previously had that
folder - well, I don't know why they had it. All sites seem to still work
fine with it (now that they all have it).
So - can I get rid of it? I don't like to clutter production servers with
unnecessary stuff where I can obviously keep it clean. If it's unnecessary
can I just delete it from all production sites, or is it part of some larger
set of operations that aspnet_regiis -i did that I'd also need to reverse? I
don't do any development on this production server (no need to connect with
VS.NET, FWIW), and no FrontPage Server Extensions are required on this box.
Thanks!