So bloody delete it. It's just a convenience thing MS does when the .NET framework is installed so that in the event that the server is intended to host .NET web apps, the directory will be available. The directory isn't even really necessary unless you plan to use Smart Nav in your .NET web apps.
- James -----Original Message----- From: S. Isaac Dealey [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 1:30 PM To: CF-Talk > If you installed the latest service pack, the .Net > framework has been > installed. Nothing is going to happen on your server just > because the > framework is installed. > The aspent_client gets installed in the webroot when the > framework gets > installed. This is just how the framework works. I wasn't talking about in the web root -- I don't care when it's placed in an obvious and logical place for M$ stuff -- it was placed within one of my own CF applications. It's _also_ in the wwwroot directory -- my problem is that MS is placing it within wwwroot/new epoch/tapestry43e -- my own non-ms application. s. isaac dealey 954-776-0046 new epoch http://www.turnkey.to lead architect, tapestry cms http://products.turnkey.to tapestry api is opensource http://www.turnkey.to/tapi certified advanced coldfusion 5 developer http://www.macromedia.com/v1/handlers/index.cfm?ID=21816 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
