We are experiencing problem while creating/viewing a form in local development environment running under local IIS.The partial view 'FormContainerBlock' was not found or no view engine supports the searched locations. The following locations were searched:~/Views/FormContainerBlock/FormContainerBlock.cshtml~/Views/FormContainerBlock/FormContainerBlock.vbhtml~/Views/Shared/FormContainerBlock.cshtml~/Views/Shared/FormContainerBlock.vbhtml~/Views/Shared/ElementBlocks/FormContainerBlock.cshtml~/SiteName/EPiServer/EPiServer.Forms/Views/ElementBlocks/FormContainerBlock.cshtml~/Views/FormContainerBlock/FormContainerBlock.aspx~/Views/FormContainerBlock/FormContainerBlock.ascx~/Views/Shared/FormContainerBlock.aspx~/Views/Shared/FormContainerBlock.ascx~/Views/Shared/ElementBlocks/FormContainerBlock.ascx~/SiteName/EPiServer/EPiServer.Forms/Views/ElementBlocks/FormContainerBlock.ascx/SiteName/Util/Views/Shared/FormContainerBlock.ascx/SiteName/Util/Views/Shared/DisplayTemplates/FormContainerBlock.ascx/SiteName/Util/Views/Shared/EditorTemplates/FormContainerBlock.ascx
The application is runnig locally under Local IIS and the name of the WebSite is SiteName.
However if the applocation runs under IIS Express or deployed on a Web Server with the proper host name (SiteName.com), all working fine as expected.
The problem happens while ruuning the application in a developer PC with Local IIS.
We are using Episerver Code 10.10.4 with Forms 4.8.0
Any help is appreciated.
Please check the path ~/SiteName/EPiServer/EPiServer.Forms/Views/ElementBlocks/FormContainerBlock.ascx The default view is here
Do you use Virtual Directory ?
Yes, in development environment, the "SiteName" is the virtual directory/application created under "Default Web Site".
I couldn't locate the file in the above path. But the file is in the modules\_protected\EPiServer.Forms\EPiServer.Forms.zip.
All is fine when we deploy the code in our staging environment where we have a propery domain name for the site.
Perhaps, the problem happens when using virtual directory.
I'll log a bug and investigate the problem. For now, please create a new site and dont use virtual directory.
Thanks for letting us know about this.
Great Quan. Much appreciated. Any follow up on this issue would be very much appreciated. Thanks.
I don't think "setup site under VD for local development, then run as standalone site in staging/prod" is a good approach. You should use a separated site in IIS for it, to mimic what you have in staging, production.
IMO, supporting VD just for local development (which is impractical in real life) worth much more effort and bring little benefit.