I develop a site with Django and PyCharm.
I just linked my project to a GitHub repository, pushed the git-ignore file to make a test, and then I closed the project, when I reopened the project, Pycharm started to make some initialization, and all my Django project has been destroyed... I tried to find some files with recuva, the only thing I founded was a xml file.
When I open the project, the github repository is not even linked anymore.
And in the right upper corner I can see one of my old html file : base.html. (see the capture).
I don't know what to do, please tell me we can do something.
This is multiple days of works who have vanished.
I resolved the problem. The Project was in the the recycle bin, I can assure you that it's the first think I have looked, and it wasn't there at the first time, and I can't explain why it was put there by the IDE.
What a panic !
Related
We have a team of several members using Eclipse for a C & C++ application that we commit the make files it generates as part of the package build. I have added and committed a library to the project then we decide against using it. So I remove it from my project and commit the change to git for the rest of the team. When anyone else pulls the change their Eclipse reverts the removal to the .cproject file preventing the removal of the unwanted library, include paths, and toolchain paths. The only thing that seems to work is to blow away the project metadata and re-import the project, which is a hassle.
How do I easily get everyone else's Eclipse to accept the removal and stop adding it back in?
Thanks.
The issue comes from not committing the .metadata folder. Eclipse keeps a backup of the project somewhere in there and continually changes these file making it unreasonable to commit to source control.
The only thing I've found to always work is to delete the project from the workspace, but do not remove the files, and import the updated project after pulling the updates from source control.
You and your team may not be able or willing to do this, but it is easier to not check in IDE specific files at all and allow a build tool plugin like Maven or Gradle to handle the project structure and classpath. This is how I've worked with team members for years without experiencing this problem.
There is quite a bit of a paradigm shift doing this, and depending on the flexibility of your project it may not be feasible.
Edit:
I noticed you are of the C persuasion. I don't recommend Maven, but consider Gradle.
https://docs.gradle.org/3.5/userguide/native_software.html
A point to note:
I recently switched to a computer that has a hybrid SSD and HDD setup, since the SSD is small enough that it is best kept for the OS alone.
The Windows partition has 60 GB of space, and access to a 500 GB partition on the HDD.
The problem:
I cloned the project files to a directory using the GitHub windows GUI (I do all version control through the GitHub GUI, rather than using the built in VS functionality).
I was able to build the solution successfully. Then, upon pressing the "Start Debugging (F5)" button, I get the following error:
Here are the relevant project properties for the project in question:
What it looks like: it looks like \.\ isn't being parsed properly as "current directory". However, this is very weird given that I don't have any issues with the same project settings on other computers. EDIT: From further explorations (see below), I later found out that its not a parsing error, since VS cannot find the file in general. So, I wonder if it has anything to do with the recent switch to a new computer, and the way hard drives are set up? I think it is unlikely to be a problem with my GitHub workflow, since GitHub does not care about the Debug directory (it is ignored).
What could the issue be?
Things I have made sure of so far:
There are no errors in the CodeChain project (i.e. the build is successful without any weird errors):
I thought this might be an issue based on some other "Unable to start program" hits I got on Google, but I am able to rule it out.
I reverted changes by deleting the new branch I was working on, and completely cleaning the project from the disk in case it was an obscure error. I then recloned to its earlier last known working state, and got the following. I still get the same error.
I know for a fact that the file exists, and I also tried using a different variable to denote the directory where the output is located:
I still get the same error:
Maybe the double slashes are a problem (but they shouldn't be, right?). So I take out the superfluous slash: $(ProjectDir)Debug\. No luck:
Surprisingly, the solution as a whole does run, when I select the main project as the startup project!
The project I am trying to open creates a static *.lib file. This cannot be opened and run.
There is no way the project I was trying to debug was opening on other computers. Rather, I probably had a different startup project selected.
Indeed, this was the issue. I had forgotten which startup project I needed, and thus was not opening the right one.
Alright so I was a few weeks into this program with no error like this until I woke up this morning and tried to run the project again. When I try to run it the build fails however there is no error of any description in either the error list or the output views. I've checked and made sure that VS is showing all errors and commented out all new code from the passed few days that I added.
I even started a new project and tested different code and it worked just fine. I've looked around the net but I can't find anything of use. I'm hoping someone here might be able to shed a little light on this for me. The project is about 24 files at this point so I'm not sure if I can really post the code.
One thing I do know is that recently a friend of mine on the same network as me accessed the project to look at it from his computer. I have no idea if this would cause this problem but I guessed I should mention it just in case it is related. I should also note I have rebuilt the project twice with no effect. The only thing I know I can do is copy and paste the code to another project but I really don't want it to come to that. Thanks in advanced.
Try to remove *.suo *.aps *.sdf in your project directory and remove Release or Debug directory which contains *.obj files.
then rebuild your project.
I was trying to set up the Eclipse on a new computer, and thought I might as well try Juno instead of Indigo as I was using before.
However, attempting to import my PyDev/Django files was troublesome, and I ended up creating a new Django project and copying my source files in.
However, when I hit Refresh, Eclipse deletes a bunch of files including urls.py!
I've given up for now - back to Notepad++ - but does anyone have any ideas as to what might be causing this?
I must say that'd be the first time I heard that PyDev was deleting .py files... (it does have an option to remove orphaned .pyc files which you can disable on window > preferences > pydev > builders > how to handle .pyc/$py.class deletion).
Are you sure that it's really deleting those files in the filesystem? Can you reproduce that? (if so, please provide the steps to do so, because I've tried many things here and haven't been able to duplicate that behavior). It'd be nice if you check if it really removes the files in the filesystem (i.e.: it's possible that for some reason it's only filtering those in the PyDev package explorer?)
I just lost 3 hours of work using pydev and eclipse, without using django. So this is not django specific.
This popup comes up as soon as the app is started:
The program can't start because MSVCP90.dll is missing from your computer.
Before anyone says "install the VC++ runtimes", wait! If I rename the folder containing my .EXE then the app runs. If I rename it back, it breaks. The app has been running for weeks without any changes to my system/VS installation (2008 SP1), we suddenly spotted this error a few days ago.
Lost as to why the name of the dir is causing issues... again this has not changed in months and all our resource paths are relative anyway, e.g "../someOtherDir/...."
It doesn't just do this on my PC, we have the /bin dir (the one containing EXE) in SVN and suddenly everyone started seeing the same issue, even though the binaries themselves seem just fine. Is it possible some additional data got put into SVN and that's the cause? Since it's not just one PC, there must be something either in SVN or the EXE itself...
Note this popup comes before our code even gets to run.
It seems that there is a .exe.manifest file lying around, specifying some other version of MSVCP90.dll. Removing this file should do the trick (In theory the manifest is the solution against dll hell, but in reality it is just a new PITA).
Try rolling back to some earlier SVN revisions and see if you can identify a change which made it stop working. A binary search will be most efficient for this. PATH settings might also be an issue?