Last post Jul 21, 2006 05:25 AM by Vinod_pawar
May 03, 2005 08:59 AM|Vinod_pawar|LINK
I have built a portal using DotNetNuke 3.0.13. Everything was working perfectly fine and then all of sudden, something went wrong and
Register Link started to redirect to Home Page. I had done some changes with pages by deleting and adding. but I don't know now what went wrong. Is anybody there who can tell me how can I get
the Register functionality of my live portal without again compiling the entire solution and deploying it.
May 03, 2005 01:49 PM|thedigitalnomad.com|LINK
From within admin reselect <none specified> as your User page and update your site settings.
That should work....
May 07, 2005 12:58 AM|Vinod_pawar|LINK
Could you elobarate a little more about this, why this must be happening? and what has gone wrong. How does Register link work?
Jul 19, 2006 08:03 AM|mukesh.tungaria|LINK
Hi Vinod Pawar,
I have been searching a lot on how to create the msi for dotnetnuke, then i found your page where you explained the automated xcopy. In that explaination you haven't described where are you linking the dotnetnuke project with that msi in the whole procedure.
Please help me as i require it very badly.
I hope you can understand my situation as you too faced it.
Thanks & Regards,
Jul 20, 2006 05:36 AM|Vinod_pawar|LINK
Jul 21, 2006 05:25 AM|Vinod_pawar|LINK
Use nant to compile your solution. After your solution is compiled, it will give you a clean copy of your project that can be put on web server as it is and after creation of a virtual directory, it'll start working.
Now, go with the following steps
1. compile your project with nant. I really don't remember how to do it but surely, you have to use command prompt and also you need to have a built file for your project. I think that should have been there somewhere in your project (.build or .built is
the ext for build file)
2. Now port this compiled version on your local server by creating a new virtual directory and test, if it works.
3. Once you are sure that the compiled version is working for you then follow the steps I have posted in p2p.wrox forum (http://p2p.wrox.com/topic.asp?TOPIC_ID=29440).
4. You are ready with MSI and now try it on your local server, perhaps with different virtual directory name`. MSI asks for virtual directory while installation (it also gives default virtual directory name that has been set in web deployment project)
5. If everything works, then you are ready with you MSI that can be deployed without any manual interference.