I have tried copying the wwwroot directory from Windows Server 2012 R2 data center on Azure Cloud to Windows 8.1 over Remote Desktop Connection and FileZilla, and the copied folder size on Windows 8.1 is much less than the source folder on the server after copy operation completion.
The Source folder size is 683MB while the copied folder is 570MB. I have only found one close explanation for this on support.microsoft.com (support.microsoft.com/en-us/kb/2891362) which explains that this might be due to long paths that exceed the maximum allowable path length.
I would appreciate if anybody have experience on such matter to enlight me.
Thank you
A typical cause of these symptoms is that you have used an ascii/text transfer mode, so all CRLF line-endings got converted to CR only (one byte less for each line).
But you have provided way too little information, so we can only guess.
Download the directory tree back (to another folder) and compare against your original source folder.
Check if the problem is specific to a certain folder/file only or if all (or majority of) files got reduced proportionally.
Related
Windows 11 (Home Single Language 21H2 OS build 22000.1281) deletes js files from the project's folders every time
System Restore Point used.
It's so frustrating to find out that you have left with an index.html
and CSS files only.
Is there any way to stop that?
The answer from the Microsoft community:
Vista list of monitored extensions is hardcoded and there is no way to change it.
I have a Windows 10 image backup from about 6 months ago that contains some code I need to recover.
The image backup was made on my prior PC, which has since suffered a catastrophic hard drive failure and was reimaged with Windows 10.
Is it possible to browse the old image backup and find and extract the folder(s) I need?
Simple, but ridiculously hard to find with Google if you don't know what to search for.
There are .vhdx files in the WindowsImageBackup folder
Find the .vhdx that represents the disk you want to mount/explore
Attach the .vhdx with diskpart or Disk Management
Assign a drive letter
Browse with File Explorer
Caveat: You might have to open a DOS cmd prompt in Admin mode and use diskpart to assign the drive a letter.
I just discovered we can turn on per directory case sensitivity on Windows 10 and that one needs to recursively enable this feature on every child directory so everything under the root folder supports case sensitivity. This is fine if I had a pre-existing directory tree I suppose.
But what if I had an existing codebase, with a set of subdirectories and files that has case sensitive names, which is hosted on a remote system (e.g. a perforce case-sensitive server) that I want to copy over to a root folder on Windows 10 that I have enabled case sensitivity on? Can I (perforce) sync first to download the codebase into the root folder and then run a recursive command (as shown here Apply setCaseSensitiveInfo recursively to all folders and subfolders) to enable case sensitivity so editors can correctly open files that just differ in case? Will that work? If not how can I achieve this?
P.S. This is the first time I'm posting here so please let me know if this question appears ambiguous in any way and I'll do my best to edit/re-post.
P.P.S. Also I'm in the middle of a transition from a Macbook to a Windows laptop and as such do not have a windows machine to try this on for myself, so I ask this question to gain understanding, that will aid in the setup of a development environment on a Windows machine. Thanks in advance!
Finally got my hands on a windows machine to test this behavior and I can confirm that cloning/sync'ing a repository with a subdirectory tree containing case sensitive files and folders, into a root folder that has the case sensitivity attribute enabled will work and applications are able to open these files correctly subsequently; the key concept here is case-sensitivity inheritance for new children!
Sure enough, I later found this article explaining the feature: https://devblogs.microsoft.com/commandline/improved-per-directory-case-sensitivity-support-in-wsl/#case-sensitivity-inheritance
Dear community members,
We have three of same hardware Windows 7 Professional computers. No one of them is connected to a domain or directory service etc.
We run same executable image on all three computers. In one of them, I had to rename it. Because, with my application's original filename, it has no write access to it's working directory.
I setup full access permisions to USER group in working directory manually but this did not solve.
I suspect some kind of deny mechanism in Windows based on executable's name.
I searched the registry for executable's name but I did not find something relevant or meaningfull.
This situation occured after lot of crashes and updates of my program on that computer (I am a developer). One day, it suddenly started not to open files. I did not touch registry or did not change something other on OS.
My executable's name is karbon_tart.exe
When it start, it calls CreateFile (open mode if exist or create mode if not exist) to open karbon_tart.log file and karbon_tart.ini file.
With the files are exist and without the file exists, I tried two times and none of them, the program can open the files.
But if I just rename the name to karbon_tart_a.exe, program can open files no matter if they are exist or not.
Thank you for your interest
Regards
Ömür Ölmez.
I figured out at the end.
It is because of an old copy of my application in Virtual Store.
I'm using multiple computers for development and I want to be able to store my files in my dropbox folder. I went to change the physical path in IIS from c:\inetpup\wwwroot to the dropbox folder but I get this error:
The requested page cannot be accessed
because the related configuration data
for the page is invalid.
I couldn't find the config file so I was wondering if anyone had done this before or whether there a better way to sync everything nicely across several PCs?
I tried it (IIS 7.5, Win 7) and it should work just fine to let your physical path of your web look at your dropfox folder. I would guess your web.config file generally contains malformed XML (see KB942055).
I'd suggest, try to map it to an empty folder just with an index.html file and see if this error still occurs.
As a workaround, I guess you can put Dropbox in your wwwroot folder and set up a virtual directory that points to Dropbox. However, there are some security issues that may hinder you from doing so. I come across a nice tutorial on how to set up Dropbox to IIS as FTP Publishing. Hope it helps.
Hodgin's guide on using Dropbox as FTP publishing.