I am looking for official documentation (preferably) that would describe when exactly Windows folder time-stamp changes. I am not sure where to look for the exact answer and any help will be appreciated.
The problem is that there is a folder in which all of the files have "changed" date coming from say 2005 while the folder changed date is 2015. What actions could (except for deleting / moving files) could have brought that change to the folder time stamp? Unfortunately I do not have access to complete metadata but only to the date of last change (screenshot).
Thanks a lot for any tip!
Related
I have downloaded latest kibana OSS zip file from here.
However I noticed its taking too long to extract the zip on Windows default zip extract utility.
Is it meant to be this much time consuming Or do I need to change anything on my machine to improve it ?
The default unzipping functionality in Windows cannot, for whatever reason, unzip Kibana. It times out when I try it and I've seen others have the same problem. I've never had this issue with anything besides Kibana, so I'm pretty confident the problem is with Kibana.
The way I unzipped it in the end was by downloading 7zip. Then I right clicked on the Kibana .zip folder and unzipped it with 7zip. Took like 5 minutes which is ridiculous but it still worked.
Get 7zip here
This is basically a known issue on Windows, but I'm not sure what can be done against it (other than convince Microsoft to add a better implementation).
An alternative ZIP client should help with the problem though if I remember correctly.
Ive made a terrible mistake and decided to make the publish folder for a VS Solution the folder of the source files.
Selecting the delete previous files prior I have removed majority of the source I was working on.
It was a small project to do a database integrity cleanse after there was a major bug found through my companies software so there is no Source Control or anything set up and had been a couple days work.
Wondering if IIS express stores a cache of these files anywhere in case I am able to restore the binaries and some other files from a previous build straight back into my source.
Banging my head.
Any help would be much appreciated!
Thanks,
I was working on my project on JDeveloper since several days, and today I wanted to create a new project related to this one so I imported all the files, but finally i decided to remove them so i selected them and clicked suppress.
I thought that would just remove them from the new project but it did erase all my classes.
Do you have any way in order to retrieve those files?
It can be related to Windows or to Oracle I don't have any clue to wich thing i have to do in order to recover those lost files.
I found the solution for those who could expect the same issue :
Right click on application source then Restore from local History.
It saved my day, i hope it'll save yours !
This issue is quite hard to explain, so I may need to add more details based on questions you may have.
I'm using TFS and Visual Studio 2013 for dev.
I have the following branches:
Development Branches
- $/ProjectName/Development/Development
- $/ProjectName/Development/201406 June
- $/ProjectName/Development/201407 July
- $/ProjectName/Development/201408 August
I have the following workspace mapping:
$/ -> C:\Projects
When a new month starts, I create a branch in dev, e.g. 201408 August, and set up the following mapping (in addition to the above top level mapping)
$/ProjectName/Development/201408 August -> C:\Projects\ProjectName\Development\Development
This helps me easily change my work spaces and pick which branch I want to use without having to change a LOT of references and things in IIS. That all always point to C:\Projects\ProjectName\Development\Development no matter what branch I work on.
Now once I'm done with my development for the month, I make sure all work is checked in (I always check in AT LEAST once a day). I then remove the work space mapping, so that everything is mapped only by the top level mapping again. I then merge Development/2014 August to Development/Development.
Once I'm happy with any merging I need to do, I check in Development/Development and the job is done.
All this is exactly how I'd like it to work, but there is a snag.
For some reason, VS remembers that the projects resided in Development/201408 August, so when I open the Development/Development solution file, the project points to Development/201408 August.
I then remove the project(s), and add it from the correct location (Development/Development). If you then look at the properties, it's changed it again to Development/201408 August again, DOH!
I found someone with a similar issue, and they said to:
Remove the offending project(s)
Save the solution
Close Visual Studio
Delete the *.suo file next to your solution
Re-open VS
Re-Add the project(s)
Save the solution
And the it would be fixed. This is true, it sorts out the problem, but I'm hoping somebody can tell me why this happens, because I have over 35 projects in my solution, and I sure as hell can't do this every month, it takes forever and is extremely annoying.
I do make sure to get latest versions again after the work space mapping changes. I also tried Get specific with overwriting all files. Nothing seems to work...
Any ideas?
EDIT
Forgot to mention, openening the sln file as XML, the path to the project is actually CORRECT, but when viewing the properties on the project from within VS, it's incorrect.
Question: Today I worked with MS Visual Sourcesafe, that is to say Microsoft's Sourcecode destruction system, which has never ever saved anything, but already destroyed much.
Today I had one more of those nasty destructive episodes:
I was working on a reporting service report (*.rdl xml files).
I was modifiying a report, so I created a copy and modified it.
The original being named FILENAME.rdl
My modified copy being named FILENAME2.rdl
I finished, saved. Checked in.
It was all correct.
I switched offline, continued to work.
Later on, I deleted filename.rdl, and renamed filename2.rdl to filename.rdl
I continued working for the rest of the day offline.
In the evening I checked in, and filename2.rdl reappeared.
I thought it had copied the old version back, so I deleted filename.rdl (from local computer and sourcesafe, via the delete keyboard button in the visual studio treeview) and wanted to rename filename2.rdl again to filename.rdl.
When I tried, I realized that filename2.rdl was just an entry that appeared in the treevieww, but not on disk... It was in that very momement that I realized that I now have a problem...
I looked in the recycle bin, but nothing there.
I tried 5 different undelete programms, and shadow copy explorer [to find out that non C drive data - such as the data partition e - is not backed up by the shadow copy service automatically...], but no luck. The file is gone.
Is it possible to still retrieve the file from sourcesafe, or does it get permanently removed when one presses the delete button in VisualStudio treeview and clicks OK on deleting it from file & sourcesafe ?
So far I found this one:
http://support.microsoft.com/?scid=kb;en-us;244019&x=11&y=7
but from that it is unclear whether the file is gone.
The problem is if it isn't there, I should redo the about one hour work this evening, because tomorrow will be a busy day.
There are 2 levels of Delete in SourceSafe. When you delete the file, if you check the "Destroy permanently" option, the file will not be recoverable. Otherwise, you can go to the Properties of its parent project and recover it later.
If it's not stored under some different version or branch of your code, I think you're out of luck.
Regardless, however: you estimate this is one hour's worth of work. You already (presumably) spend some amount of time (probably an hour or two) trying to get the file back. Are you not now at the point where, even if VSS has a way to get your file back for you, you'd be better served just rebuilding it?
Short answer - definitely NO!
It can't! I tried.
But it overwrote the recreated report with a completely wrong recovered version...
Fortunately, I've forseen this, and made a backup copy of the recreated report for this case.
So I didn't spend that one hour of recreating the report in vain.
This program should be forbidden, with noncompliance to this prohibition being subject to the death penalty.