Last post Aug 18, 2005 12:16 PM by Cornelius
Aug 18, 2005 04:54 AM|Cornelius|LINK
Aug 18, 2005 08:34 AM|Cornelius|LINK
Aug 18, 2005 11:19 AM|iwonder|LINK
You can use any available drive for the physical location of your DNN folder. The trick is to give proper folder permissions to it. On my workstation at home, I have various versions setup on f:, g:, e:, and x: and because these are all local installations
for testing and developing, I just give the ASP.Net worker process all privs to the root drive, but others doing this type of thing would only give permissions to enable read/write access to the folders, could be something different, but the point is - permissions
play into this type of setup.
Others with more knowledge about doing this kind of setup, could give you more detail, and probably will. I just wanted to give you a heads up.
Aug 18, 2005 12:16 PM|Cornelius|LINK
Yes, I'm ok with you. It's what I do usually untill dnn3013 and it worked fine. For 3.1 as others, I gave full control for aspnet account to my root dotnetnuke directory. This behavior is strange and I reproduce the bug on two machines.
But if it's ok for everyone, the problem come from my personnal install, so I'm going to investigate.
Thanks for help iwonder.