Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
AI OnAI Off
Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
http://localhost:7117/customerUI/edit and http://localhost:7117/customerUI/admin are the paths for Edit and Admin mode. When it comes to deployment, I usually use a tool called UnleashIt, I've a blog post describing how to use it here: http://www.frederikvig.com/2009/12/part-8-preparing-for-launch-create-an-episerver-site-from-scratch/. I've also been looking at Web Deploy, but haven't gotten around to testing it out yet :).
I recently started working on a project that I have not been in contact with from the start and since developing for EPiServer is quite new to me, I have a couple of thoughts / questions regarding the approach I need to take.
For starters; How do I identify the UI / Util-path? In the web-config I found the siteSettings-tag with the attribute uiUrl to uiUrl="http://localhost:7117/customerUI/"
However when I start it up, I get a 404 at that address ( http://localhost:7117 works )
Any thoughts on that?
Second I am looking for information about deployment capabilities with episerver/vs2008 if I do not have direct contact with the production server, hence the site is for internal use only where I cant access it. Is it possible to create some sort of a Setup project as you can with WebServices in general? If so, what should one think of while doing it?
Hope there's someone with answers out there!
/F