Last post Dec 22, 2005 04:34 PM by xddg
Jan 24, 2005 06:07 PM|Kepler|LINK
Jan 26, 2005 12:49 PM|Kepler|LINK
Jan 27, 2005 06:34 PM|walkerstewart|LINK
Dec 21, 2005 04:08 PM|andresjoaquin|LINK
I have the same problem. Did you resolve it?
Dec 22, 2005 02:20 PM|Kepler|LINK
Dec 22, 2005 04:34 PM|xddg|LINK
You need to ensure the aspnet_client folders are in your root folder. Go to the C:\Inetpub\wwwroot folder and copy the aspnet_client folder and place into the root directory of your website - This will solve the problem.
Basically in DNN, when you manually create a site - like most of us do, you are missing the aspnet client folders that sit inside every site that uses .net infrastructure. It's automatically placed there when you use a wizard I think but most people setting
up a DNN site do it manually - eg.. open IIS and browse to the folder -that's what the instructions say - but it doensn't put in the very important file aspnet_client which can cause some problems for some people. (don't you just love it - random problems
for some - hard to pinpoint)
But generally speaking you should be able to browse via windows explorer to your www folder that is setup automatically when installing IIS and see if there is a folder in there called aspnet_client - in there if you double click you'll find there should
be reference to two folders - called v1.0.3705 and v1.1.4322. They relate back to the files sitting here - C:\WINDOWS\Microsoft.NET\Framework.
Also - sometimes (favourite word here) clicking through can often step over the problem if you don't have access to the file. But not all the times!!
I hope this helps.
// edit - this might not be for all js problems but is a common problem with DNN sites installed manually and 3.08 isn't available any more anyway.