I have a project that has gone through several iterations (for different clients) and will continue to go through more. By this point, I know that when I start a new instance of this project, there are certain things that need to be done to get the new project up and running.
Rather than create these issues by hand each time, I'd like to start new instances of this project with default issues. I've read through the redmine wiki, but don't see an explicit way to do this.
I know you can copy existing issues, and it is even possible to copy multiple issues at once. (in the issues page, select them and right click on one of them)
Maybe the easiest way is to copy the issues from a previous project and assign them to the new project.
Related
Essentially I have a course that I am doing and we have many small projects and websites we make. I am a beginner so please don't use any advanced topics or knowledge. I just need a way to organize my projects. I was thinking about have a new branch for each project but the problem with that is but I have these banners pop up. Another question is that when I create a new branch does it copy only from the most recent checked out branch? If so how do I change it to copy from main?
What would be the best way to organize my web projects on Github?
I deleted part of my code, and accidentally saved.
I tried looking at my history and my source explorer, but those were both greyed out.
Help?
Thanks
I'm not sure if you can pull your deleted code out of the void, but you should look into version control software, like Git, to keep a lock on each version of your programs. I know it doesn't solve your problem now, but it will help a ton in the future if you make changes often!
Go to "Edit" → "Undo" to undo recent changes.
Or, go into your version control system's log and revert to an older committed version.
Or, restore from one of your off-site backups.
The most important was already said. However, here some relevant complements:
The Edit -> Undo (or Ctrl+Z) has to be done file by file if you have several files in your project.
The Undo works after a Save, provided that you've set the focus in the editor's window (and not the solution explorer's). However, once you've left Visual Studio, it's lost forever!
The AutoRecover setting in the Environment section of the Option dialog box ensures that a copy of your unsaved work is saved every couple of minutes and keep it a couple of days (in your document folder under Visual Studio 20xx\Backup Files...). Unfortunately, it is designed to protect you against a crash; so the files are removed when you save, and it won't help you (I mention it only in case you were aware of the backup files and hoped to get a solution with it).
If you're working with windows 10 and have activated the file history backup you may luckily look at older versions in the explorer. This will not help if you have done changes and deleted them without a backup in-between (e.g within one hour at least).
You may not like this suggestion because the VS IDE is very comfortable, once you're used to it. But some programming editors allow you to set the configuration to make a backup of the files before you save them (e.g. such as for example emacs or atom). The purpose is exactly to prevent the kind of problems that you've just mentioned.
The best approach to avoid loosing previous work is of course the source code version control, with the corresponding discipline. It's easy to setup: a right-click on your solution in the solution explorer to activate this feature on your project, then at each significant change, again a right-click on the solution to commit the changes. With git, you don't even need to create a central repository if you're working alone on smaller projects. The local repository is sufficient to archive the successive versions of your code and find them back. But again, it's no magic: if you've made a lot of changes and didn't commit them, it won't retrieve them...
I've got the good fortune to be stuck in Visual C++ 6 (don't laugh at me too hard), and the project I'm working on makes use of many different build configurations. While I guess I can create the new configuration manually by modifying the .dsp file, I'd really rather not do that out of fear that I's miss something. I don't know enough about this ancient codebase to make a new configuration from scratch, and unfortunately (ok, maybe fortunately) everybody who's ever worked on this code was either fired or quit.
Anyway, I'd like to rename some of the project configurations so that I can copy them and make a new one based off of them. This will all make sense in a second (maybe someone can suggest another idea as well).
As you can see, the old project configuration names are too long for the combo box; and too similar for me to distinguish between them. Unfortunately, the combobox is not expandable and has no tooltips; so I'm taking a stab in the dark when selecting a configuration to copy settings from.
So I was thinking, if I could figure out how to rename the ones I want to copy from, I can stick a stray character in front of them so that I can distinguish them from each other, but alas I can't even figure out how to do that.
I would like to reuse one installation of Sitecore every time I need to make code changes. I currently have a branch to fix a problem, but now I need to create another branch to fix another problem. The problems are in different websites so I need to keep the seperate branches. I really do not want to create another Sitecore installation for this second branch. Is there a way to "swap" out these solutions and "reuse" the same Sitecore installation?
Mark Ursino's comment about removing the code got me to thinking. Since the solution binded to the Sitecore installation resides in the Website folder, I'll map both solutions to somewhere arbitrary, like "Sitecore Dev Folder", and then map the branch I'm working in to the Website folder of the Sitecore installation. When I change the mapping, the solution will download from TFS into the Website folder (blowing away the existing solutuion.) And that's how I can achieve the "swapping" of solutions.
Yep, we need more info here to really answer the question.
But... in general, I would advise you not to do this. Creating a new Sitecore installation is a piece of cake with the installer, and not exactly resource intensive. You could have it use the same DB if necessary to make things easier.
Mixing two different branches with the same Sitecore instance... it seems inevitable that something would get "F'd up", to use the technical term.
I have a list of webservices from a Flex project. I am trying to load the project on a new machine and it has forgotten all the web services from the list.
I copied over the original settings file to :
"myproject-web\.settings\webservices.xml"
This contains quite a lot of webservices and I don't want to have to reimport them all. This would involve deleting all the generated code and going through one by one and adding them.
The problem is that when I go to 'Data > Manage Web Services' I don't see any of these items.
So i tried the obvious :
add a new webservice
check that the webservices.xml file was modified. in fact the new service is appended to the contents of that file
close and reopen Flex Builder
the list only contains the one new service I added and not the old ones.
How can I 'trick' Flexbuilder into recognizing the other web services in the list. It must be storing a list somewhere else.
Note: This is the same question here from months ago, but no answer.
I ran into this problem too. What I had to do was copy the wsdl.xml file from the workspace's .metadata.plugins\com.adobe.flexbuilder.webservices folder from one computer to the other.
Personally this feels like the wrong place for this since the information about what web services are being used is part of the project not the workspace. If you examine the content of that file it even has your project name in it so it knows it is project specific data. Perhaps it is here because it is a limitation of eclipse, but I suspect not. Perhaps Adobe should consider modifying the eclipse plug-in to store this data somewhere in the project files.