I'm doing a school coding project using Android Studio with Google Drive to store my app files. Google Drive is generating these desktop.ini files. Every time I delete or modify them, they are regenerated, even when I shut down Google Drive. How can I fix this? I cannot run or debug my project with this error.
As a matter of fact the desktop.ini file is created only in Google Drive folder. So you can't blame it on Windows. If it is Windows, then the file should be everywhere. Also, if you open the desktop.ini in Notepad you will see the following lines:
[.ShellClassInfo]
InfoTip=This folder is shared online.
IconFile=C:\Program Files\Google\Drive\googledrivesync.exe
IconIndex=16
See InfoTip and IconFile. There is no way Windows would be doing this.
I got my solution：
1）Open ini file's Property Dialog
2）Hide this file in System File way，use this cmd：attrib +h +s "D:\Google Docs\desktop.ini" /s /d
3）Deny all Access Privilage in Property Dialog，like this：
4）Just refresh folder！
Desktop.ini files are generated by Windows, not Google Drive. When you open a folder in Windows, it creates a desktop.ini file. The desktop.ini file stores the view settings for that folder.
As to why you are getting build errors in Android Studio simply because this file exists, I can't answer at the moment. I have successfully built many Android projects in Android Studio with that file in the folder.
Related
Hi DocuSign CLM geeks and the DocuSign API in-house team-
Our team will be using DocuSign CLM with the DocuSign Edit add-on to easily open Microsoft Word files and save back to CLM.
We'd like to include the installation of DocuSign Edit in our Silent Mode installation configuration. We're hoping there's an msi File available for the DocuSign Edit extension? If so, please link!
Plan B- If we were to make our own msi from the available exe, does anyone have a trail stomped out for doing this? (a blog post, documentation, step by step, video demo, even a horror story)
Thanks for tips.
https://tools.springcm.com/sites/default/files/apps/docusign-edit-pc-2.01.00.exe
This is an exe that is built from an MSI, so it is an MSI.
If you want to get the MSI out of this https://www.codetwo.com/kb/msi-from-exe/:
The first method is based on the fact that most installers extract their .msi files to the temporary files folder during the installation process. To extract an MSI file from an EXE installer, you need to:
Launch your .exe file.
When you see the first prompt (e.g. a question about whether you want to continue installation, accept a license agreement, etc.), do not click anything in this window and do not close it.
Open Windows Explorer, type %temp% in the address bar and press Enter.
Sort the files in the folder by the modification date. The newest file on the list should be the .msi file you are looking for.
Copy the MSI file to a safe location before you close the installer prompt window (see step 2). Be aware that if you close the installer window, the MSI file will be immediately deleted from the temporary files folder.
The second method uses a free third-party tool called 7-Zip to browse the content of the .exe installer file. Follow the steps below.
Download 7-Zip from this page and install it.
Right-click on the .exe file (from which you want to extract an .msi file) and from the shortcut menu choose 7-Zip > Open Archive.
Do not extract any files yet. Instead, browse and look for the folder MSI within the contents. It might take some time to find this folder because it is not always located directly in the root directory (its location may vary depending on the installer).
When you locate the MSI folder, you will notice that it most likely does not contain any .msi files, but a file or files with no extensions and rather cryptic names such as 132. Despite these misleading names, these are actually the MSI files you are looking for.
Drag and drop these files to any desired folder or select them and extract them with 7-Zip. Close 7-Zip after that.
Change the names of the extracted files so that they include the .msi extension.
If there are two files, the larger one is the 64-bit installer, and the smaller one is the 32-bit version. Use the one you need.
Finally, if you want to tweak an MSI, you can use the Orca tool by Microsoft - https://learn.microsoft.com/en-us/windows/win32/msi/orca-exe
I am trying to access the Device File Explorer but I keep getting Permission denied. Have not been able to find a solution online anywhere. Any help would be greatly appreciated!
Android Studio photo
I had a similar problem: I could not access storage\emulated because it kept telling me that I had no permissions.
I found no answers on internet, but I created a new emulator (Nexus_One) with android's version lollipop (5.1), and at first I did not find any directory inside storage. I right clicked, selected upload and uploaded a file. Then I could see all the directories inside storage. I right clicked on emulated, uploaded a file, and finally got the directory 0 where I needed to upload the real file.
However, this trick did not work on the emulators I already had (Nexux 5).
It is not a solution, but I hope it helps!
'/storage/emulated/0/' like a abstract path, you can upload file on sdcard/,and visit it use '/storage/emulated/0/' in android code.For example,if you want to visit a test.txt in '/storage/emulated/0/myFiles/test/test.txt'(code path), you should upload the test.txt in 'sdcard/test/test.txt'(in Device File Explorer,AS).
After adding a web role to my Azure project I get a build error within my Visual Studio Team Services environment. Though, I cannot figure out what is causing this. Where is AssemblyAttributes.cs comming from? I cannot find this file in my solution folder.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Windows Azure Tools\2.7\Microsoft.WindowsAzure.targets (2787, 5)
Unable to copy file "C:\Users\buildguest\AppData\Local\Temp\.NETFramework,Version=v4.5.2.AssemblyAttributes.cs" to "C:\a\6e05cef4\xxxx\xxxx.Backend.Api.Azure\obj\Debug\Tijdmunt.Ui.WebRole\C:\Users\buildguest\AppData\Local\Temp\.NETFramework,Version=v4.5.2.AssemblyAttributes.cs". The given path's format is not supported.
AssemblyAttributes.cs is a temporary generated file created by MSBuild, so It's not going to be on your solution. Instead it is going to be under the temporary folder.
Since It's a temporary file and created on every build, I just went to below location and deleted the file, then my solution started to be successfully building again.
C:\Users\UserName\AppData\Local\Temp.NETFramework,Version=v4.5.AssemblyAttributes.cs
Hope this helps someone else.
I'm trying to map a folder from TFS, and it fouls it up every time I re-try doing it.
My structure on server is:
$/
--tool
----ASK
------Project1
------Project2
------Project3
------etc
I map to a local folder: C:\mytool and do a get. It correctly downloads all the folders in this structure:
C:/mytool
--tool
----ASK
------Project1
------Project2
------Project3
------etc
However, when I try to open ASK.sln (located in C:/mytool/tool folder) It fails when it tries to open projects.
Instead of opening
C:\mytool\tool\ASK\Project1
it complains that it can't find the project at
C:\mytool\tool\mytool\tool\Project1
and same for other projects, i.e.
C:\mytool\tool\mytool\tool\Project2
C:\mytool\tool\mytool\tool\Project3
Please help!
I've tried deleting everything, mapping C:\mytool to tool instead of '$/' and also to 'ASK' and every time it tries searching for projects in the wrong location.
iTunes File Sharing for iOS apps allows users to pull down folders from apps via syncing to the device but it doesn't allow the reverse and load in directories from a computer to the device. Is there a way to make a in-app folder a bundle/package like a .app package so that the OS thinks it is a file rather than a directory?
From what I can tell GarageBand for the iPad is doing exactly this for files off the device. The context menu on the exported file in the Finder allows you to "Show Package Contents".
I appended a made up extension to the directory path and it shows up in iTunes as a file, but on export it comes out as a directory.
The following worked for me:
Rename folder to <foldername>.pkg
Drag it into the file sharing panel
In the file sharing panel, rename it back to <foldername>
I just found! Windows users can use iExplorer!
Start iExplorer (available at this URL http://www.macroplant.com/iexplorer/)
Connect iOS device to PC using USB cable
Find this folder: "Apps" > [YOUR_APP] > "Documents"
Drag and Drop the bundle/package into "Documents" folder
Note: A bundle/package on Mac is simply a folder on Windows. There is no need to have any file extension like .pkg on Windows.