Hello All
We've had this problem since we started using the Telerik controls, and I was hoping for a fix.
ANY control we use comes with the Telerik.web.ui dll or xml file.
When we try and publish a site we get an access denied on either the dll or the xml file. This locks up Visual Studio 2010 and causes us to have to reboot. Stopping the devenv.exe *32 process is not an option, because we can not kill it off. We get Access Denied, and have to reboot our PC's
We are all domain admins and local admins so this doesn't seem to be a security issue.
This happens when we build web sites, or web applications.
We have tried publishing to the local machine. That works, then hand copying to the server. Most of the time the copy hangs on the Telerik.Web.UI.xml file. Sometimes it's the .dll, and locks up file explorer.
Any and all help would be great as my developers are about to abandon using your controls.
Thanks
Gary
We've had this problem since we started using the Telerik controls, and I was hoping for a fix.
ANY control we use comes with the Telerik.web.ui dll or xml file.
When we try and publish a site we get an access denied on either the dll or the xml file. This locks up Visual Studio 2010 and causes us to have to reboot. Stopping the devenv.exe *32 process is not an option, because we can not kill it off. We get Access Denied, and have to reboot our PC's
We are all domain admins and local admins so this doesn't seem to be a security issue.
This happens when we build web sites, or web applications.
We have tried publishing to the local machine. That works, then hand copying to the server. Most of the time the copy hangs on the Telerik.Web.UI.xml file. Sometimes it's the .dll, and locks up file explorer.
Any and all help would be great as my developers are about to abandon using your controls.
Thanks
Gary
1 Answer, 1 is accepted
0
Hello Gary,
The locked files could be a result of project debugging. When using the local IIS or the ASP.NET deployment server to test locally, the DLL files are being used from these processes.
One option is to use the Clean command of the VS Project before deploying.
Another option is to stop the process that is using the DLL or the XML file.
If you still have issues with this matter, please contact us through a proper support ticket with details about the deployment steps leading to the issue and the exact configuration used to deploy the application.
Regards,
Ianko
Telerik
The locked files could be a result of project debugging. When using the local IIS or the ASP.NET deployment server to test locally, the DLL files are being used from these processes.
One option is to use the Clean command of the VS Project before deploying.
Another option is to stop the process that is using the DLL or the XML file.
If you still have issues with this matter, please contact us through a proper support ticket with details about the deployment steps leading to the issue and the exact configuration used to deploy the application.
Regards,
Ianko
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.