Reputation: 6590
I am starting to develop windows 8 app. I am new in windows 8 app development. I have one page i.e. MainPage.xaml. I am not able to see the design view. It gives an error.
System.Security.SecurityException
Designer could not be started because of a permissions issue on the drive to which it is installed. Please check the permissions of the folder before trying to start the designer. at Microsoft.Expression.HostUtility.Platform.AppContainerProcessDomainFactory.CreateDesignerProcess(String applicationPath, String clientPort, Uri hostUri, IDictionary environmentVariables, Int32& processId, Object& processData) at Microsoft.Expression.DesignHost.Isolation.Primitives.ProcessDomainFactory.ProcessIsolationDomain..ctor(ProcessDomainFactory factory, IIsolationBoundary boundary, AppDomainSetup appDomainInfo, FrameworkName targetFramework, String identifier, String baseDirectory) at Microsoft.Expression.DesignHost.Isolation.Primitives.ProcessDomainFactory.CreateIsolationDomain(IIsolationBoundary boundary) at Microsoft.Expression.HostUtility.Platform.AppContainerProcessDomainFactory.CreateIsolationDomain(IIsolationBoundary boundary) at Microsoft.Expression.DesignHost.Isolation.Primitives.IsolationBoundary.Initialize() at Microsoft.Expression.DesignHost.Isolation.Primitives.IsolationBoundary.CreateInstance[T](Type type) at Microsoft.Expression.DesignHost.Isolation.IsolatedExportProvider.Initialize() at Microsoft.VisualStudio.ExpressionHost.Services.VSIsolationService.CreateExportProvider(IIsolationTarget isolationTarget, ICatalogFactory catalogFactory, IExportFilter filter) at Microsoft.Expression.DesignHost.Isolation.IsolationService.CreateLease(IIsolationTarget isolationTarget) at Microsoft.Expression.DesignHost.IsolatedDesignerService.CreateLease(IIsolationTarget isolationTarget, CancellationToken cancelToken, DesignerServiceEntry& entry) at Microsoft.Expression.DesignHost.IsolatedDesignerService.IsolatedDesignerView.CreateDesignerViewInfo(CancellationToken cancelToken) at Microsoft.Expression.DesignHost.Isolation.IsolatedTaskScheduler.InvokeWithCulture[T](CultureInfo culture, Func
2 func, CancellationToken cancelToken) at Microsoft.Expression.DesignHost.Isolation.IsolatedTaskScheduler.<>c__DisplayClassa
1.b__6() at System.Threading.Tasks.Task`1.InnerInvoke() at System.Threading.Tasks.Task.Execute()
I have given administrative rights to the folders. But I am not getting why this error is getting?
Can someone please help me to solve this ?
Upvotes: 1
Views: 3445
Reputation: 9
I have just upgraded from Windows 7 to Windows 10
And the first problem i had with Windows 10 is this(besides the one where you need to enable "Developer mode" this is probably only in windows 10), and the trick for me that made this work was running Visual Studio 2013 as Admin
Hope this helps
Upvotes: 1
Reputation: 4899
I will just try to help with some steps and links as it is not reproduce able on my sid e:)
Steps:
THIS MUST BE DONE AS ADMINISTRATOR
Now support links if the steps don't work
this is not only in windows 8 it happened with me in windows 7 when I was in silverlight but I managed to fix some how .. But now in metro apps I still don't get this error :) Please try and let me know
Upvotes: 0
Reputation: 1
Just run Visual Studio as Administrator. When it asks for permission to run the designer click ok and wait.
Upvotes: 0
Reputation: 1982
I encountered the identical problem recently while developing a Windows Phone 8.1 ARM application, and was stumped until I amalgamated several posts from the Web.
(1) I ran "devenv.exe /resetsettings". This removed the "System.Security.SecurityException" error, but left me with the message "Design view is unavailable for x64 and ARM target platforms".
(2) At this point it seems the Visual Studio Designer does not work when the Solution Platform (the drop-down combo box in the middle of the tool bar) is set to "ARM". The workaround is to temporarily set the Solution Platform to "WIN32", do what you need to, set the Solution Platform back to "ARM", and compile.
Although a slight pain, it now works for me.
Upvotes: 0
Reputation: 1452
I upgraded from Win 7 to Win 8.1 and faced with the same issue.
I solved it like this:
that's it!
Upvotes: 0