Last post Apr 06, 2005 11:13 PM by DougV
Apr 06, 2005 09:26 PM|pauldes|LINK
New to DNN. My only experience in doing web sites, I have always developed and tested on my local PC, then posted the files and updated the database definitions remotely. Does this practice hold true for DNN?
Are there certain functions I can only perform on the remote site, so that it's not possible to develop locally, then upload? Do I end up repeating some tasks both locally and remotely so that I keep my test and production environment in synch? Is there
anywhere I can read about this?
Apr 06, 2005 11:13 PM|DougV|LINK
I started out writing web sites with Frontpage, then moved to IBS, now I wouldn't trade DotNetNuke for anything. In the beginning I had to do very much as you have mentioned, "develop and test local", then upload the whole mess to the host.
With DNN, creating content is as easy as posting to this forum you are now reading.
To answer your question, "Are there certain functions I can only perform on the remote site, so that it's not possible to develop locally, then upload?" If you have Internet Information Services on your PC, then you can
do anything local and you will probably prefer to do it local first. You need XP Pro for IIs.
"Do I end up repeating some tasks both locally and remotely so that I keep my test and production environment in synch?"
None that I can think of. When you get finished working on something (like skin or custom module) locally, you then just upload it to your site and your done. The content gets edited directly on your remote site so you don't
upload it and there's nothing to worry about synching (usually).
Where to read more? Start out on http://www.dotnetnuke.com and follow links from there. Lots of info in the DNN zip files. There are a couple of books coming out also.