Getting this error when trying to debug a Windows Universal App. Per MSDN, error 0x80073D1F is ERROR_REGISTRATION_FROM_REMOTE_DRIVE_NOT_SUPPORTED. But in my scenario, I'm not using a remote drive.
I'm not using a remote drive, but I have a folder on a local drive for sources that's mapped as a separate volume. I guess that makes it appear to the app deployment logic like a remote drive. I navigated to the folder on the local drive (not the mapped volume) and opened the VS solution from there, and the deployment works.
Related
I am a high school CS teacher teaching C++ with Xcode. In the past, I have used Google Backup and Sync such that my kids shared a Google Drive folder with me, saved all their work locally in their Google Drive folder, and synced this folder with Google Drive's cloud. Worked like a charm. Now, our school has transitioned to Google FileStream, which works differently. Google Drive is now treated as a mounted volume and by default does not copy synced folders, but provides links to them on the cloud, so they appear to be local, but are in fact not. I am able to have my kids set their class folder in "offline mode" so that they can use it as before, maintaining local file copies as well as syncing with Google Drive's cloud. However, I just discovered that this results in a "permission denied" error when trying to execute their code. Projects build, but do not run.
I had them move their project folders to their desktop, and they build and run just fine. When saved on the FileStream mount, even attempting to run a successfully built project through terminal results in the same "permission denied" response. So I am 100% sure the issue here is trying to run executable code from the FileStream mounted folder.
Any thoughts here? Is there a Mac security setting somewhere that I cannot find that will allow this? Or is this a Google Drive thing? I can always have them work locally, then copy the project over, but that is a real pain for them and me with grading from home.
i'm trying to remote debug my windows tablet store app and when i go to debug it on the remote machine i get this error.
i have done both ways it asks me to fix it in the image but i keep getting the same result. the tablet has the remote manager installed on it with the update version downloaded from Microsoft.
I uninstalled the app installation folders on the remote machine and received a different issue. " Could not generate the root folder for app, Illegal characters in path. "
answer was found here
I have created an installer in Visual Studios 2010 and i added some custom actions. It is meant to be a workstation installer so it would check to see if certain files exist in the destination folder and move shortcuts around after. However if i use a UNC path or a mapped network drive path as the destination folder and use the commands My.Computer.FileSystem.FileExists and System.IO.File.Exists they return false on a network drive. Is there a way to figure out in a custom action if the file exists. Currently I am using Windows XP to run the installer so UAC is not a factor here.
Custom actions in a VS setup project run with the system account, which has no network privileges and so can't get to see them. Also, mapped drives are a user-profile thing, not system-wide, so they belong to a particular user, so the system account won't see them because of that too.
So there isn't a good way to do this. It might work if the custom action ran with the installing user's account, but then it would not be elevated, and you'd need to go into the CustomAction table in the MSI file and turn off the the msidbCustomActionTypeNoImpersonate bit.
https://msdn.microsoft.com/en-us/library/aa368069(v=vs.85).aspx
The problem is put as follows:
I installed my VS2013 on a FAT32 disk and it works nice except with windows 8 app development, where the XAML designer just won't open while requesting elevated privilege of running "icacls" commands, of which I approves of course, to modify the permission on the IDE folder to gain access to it, only to fail because it's FAT32 and it just doesn't have any permission mechanism. As a result, the designer says that it doesn't have the permission to specific folders, which makes no sense to me.
Previously I installed VS2012 on C: partition, which was NTFS and ran into the same issue. However, I solved it by assigning proper permission on destination folders. Yet this time, it doesn't work in that it has no option for permission and security on a FAT32 partition except "hidden" and "readonly". I have also tried other tricky ways like trying to link the IDE folder to a duplicate on a NTFS partition, but haven't found the solution yet.
Is there anyone out there who knows any workaround or runs into the same issue?
FYI, the exception thrown by VS designer:
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.
I have a pc and laptop. When I am in university I work on a project (Or soloution) on my laptop. When I get back home I really want to work on the project using my PC (I got dual screen and ofcourse my PC is thusands time faster!).
The projects are located in Documents\Visual Studio...... in my laptop and of course this folder is shared on the HomeGroup.
I can open the project in my PC but when I try to build the project I get some errors like this:
Error 1 Unexpected error creating debug information file '\\AMIGA\Users\Sean\Documents\Visual Studio 2010\Projects\MiniScope\MiniScope\obj\Debug\MiniScope.PDB' -- '\\AMIGA\Users\Sean\Documents\Visual Studio 2010\Projects\MiniScope\MiniScope\obj\Debug\MiniScope.pdb: Access is denied.
' MiniScope
And a warning like this:
Warning 2 Could not read state file "obj\Debug\ResolveAssemblyReference.cache". Access to the path '\\AMIGA\Users\Sean\Documents\Visual Studio 2010\Projects\MiniScope\MiniScope\obj\Debug\ResolveAssemblyReference.cache' is denied. MiniScope
Can someone tell me please how can I grant permission to this projects so they can compile and run?!
It's a security feature of Visual Studio. Network drives are considered untrusted (as others might change code or inject malicious stuff while you're working on it).
As a solution to this, I'd suggest not using a network share. Instead, use a tool to synchronize folders or a file hosting service such as Dropbox, SkyDrive or Box.net.
I never used the other two services, but Dropbox allows you to work with your Dropbox folder like any other folder (it's essentially just a standard folder observed by the service). Any modifications inside are mirrored on their server (secured/encrypted) and any PC or Android device you link with it. So you could link your PC and your Laptop, and the tool would do the syncing for you (using the internet or LAN, whichever is available (and faster)).