As evident from title, I entered a bug in MantisBT but mistaken choose wrong project. I can go back and edit most of the parameters of bug but it doesn't allow me to change the project. I looked in configuration and there seems to be no option for that there as well. Is there a way I fix the bug information by changing the project to the correct value?
You can move issues between projects if your system configuration and access levels allow it (look for the Move button in the View Issue Details page)
You can also move multiple issues by doing the following:
Go to View Issues page.
Filter on the issues you want to move (optional)
Tick the issues from the list that you want to move or select all.
Go to the bottom of the list and select "Move" then click Go.
Select project to move to.
Note that since MantisBT uses a universal id across all projects, moving an issue doesn't break links to it, since URL to the issue will remain the same.
Related
I have been working for a few days now making a simple web page to be a basic cv/bio. I started by making my headers for the page and some simple animations when switching window sizes. After playing with adding some different colors in, I noticed that an asset I added, wasn't transparent(as I had intended it to be).
That said, I have tried to delete the item from the assets Library to no avail. I've tried removing all relevant keyframes, as well as trying to delete it from the Master Rules. The program will not allow me to delete the item, except from the Library, which does not affect the item on the page whatsoever.
I may well be missing something completely obvious and shall feel a fool when this is answered. Thank you for your help in advance!
To delete a layer, click on it in the timeline so that it's highlighted and then press the Delete key on your keyboard.
If the element is an asset imported by you, for example a picture, you must select it at the library collapsible menu and click the trash. If you can't find this menu, clic on Menu > Window > Library.
On Responsive window, click Edit base document. You can now delete it.
I am trying to put several existing projects in one blank solution. This solution plus existing projects then need to be added to TFS source control.
Is there any way to achieve this? I simply am not able to find out how to get this done. Adding the project to a blank solution is relatively easy. Except it only places references to the existing project, rather than adding the files to the solution.
So when checking-in at sourcecontrol, it does not recognise the projectfiles as they do not get added to the solution, just references.
How can I get this done?
I managed to figure it out.
Add projectfiles of the project to be added to the solutiondirectory.
Add a reference to existing project (the one now in your solution directory).
In Windows Explorer, rightclick on the projectmap you just added and navigate to "Team Foundation Server" --> "Add".
The showing messagebox will describe which files will be added (they should be ONLY projectfiles, no bindirectory or anything).
Then reopen the solution in Visual Studio and the project should appear to be in source control.
Edit: The changes to show up in the pending-changeswindow, you just have to add them manually. They should show as "detected". Select these to be promoted and you should be able to check them in.
I've searched all over for a solution and have not been able to get them to work.
My company's product used to have the Repair option when selecting the product in the Programs and Features dialog. You could also right click on the product and select Repair there as well. Just before I inherited the installer projects, this Repair option disappeared. I looked around to see if anything was disabling this option and couldn't find anything.
In InstallShield DisableRepair is set to No. There also is no registry key set in the Uninstall section for the product for NoRepair when the product is installed. By default, I believe I should be seeing the Repair option and don't understand why it's not there. I've tried messing with ARPNOREPAIR in custom actions, all to no avail. I even created a registry key for NoRepair with both 0 and 1 for DWORD values to see if it actually would work and it did not. I'd like to say that there is some code somewhere that is disabling it, but I've checked everywhere and even talked to the previous installer coworker and he doesn't know of anything removing that option.
Does anyone have information on this?
After lots of digging around and testing I have found out some interesting things and a solution to my issue. It turns out that there was a C# custom action that was creating a separate registry entry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. Also, ARPSYSTEMCOMPONENT was being set to 1 in InstallShield which was disabling the original entry from showing in Programs and Features, while the new entry was set to show. Apparently NoModify and NoRemove work with the new entry, but not NoRepair(no idea why this is). My solution was to go back to the original entry and modify the keys that I was adding in the custom action.
I'm using the Ribbon control located on CodePlex, and following the tutorial located here . Once I add the reference, and the proper code in the designer I get this error when I try to view the form:
Exception of type 'System.ComponentModel.Design.ExceptionCollection' was thrown
And I cant figure out what I'm doing wrong. Anyone worked with this control and know how to resolve this issue?
Interesting; I just ran into this same issue with one of my own forms; which is how I found your relevant and recent question.
Here's how I solved it:
Open two instances of Visual Studio. Open the same project in both.
In one instance, goto Debug->Exceptions and enable all the 'Thrown' options to stop at first chance exceptions. This will stop the debugger when the exception is generated.
In the same instance, select Debug->Attach to Process, select devenv.exe.
In the other instance, open the form to cause the exception
With any luck the first instance should stop somewhere that yields a more relevant exception.
In my case it turned out to be something that I should have conditioned with:
if (!DesignMode)
{
// Do something that should only happen at runtime
}
Don't forget turn turn off all those 'Thrown' options later.
A workaround for me was:
Right-click on the form and 'View Code'
Keep the code loaded in the editor and then attempt to view the designer again.
This feels very glitchy and I cannot confirm whether it's a problem with my code (as I'm working on an entirely new codebase) or whether it's a VS2012 bug. If I find out, I will report back.
Since the solution outlined by pilotcam didn't work for me, I took a different approach:
Make a SVN commit for the file.
Open the “*.designer.cs” file of the form that shows the error in source view.
Remove larger blocks of form element declarations.
Fix all compilation errors with ReSharper (i.e. ensure that nothing is red anymore on the side-indicator).
Save the file. No need to compile.
Open the Windows Forms Designer of the form.
If the error still shows up, do a SVN revert to go back to the initial state.
Repeat steps 2 to 7 until the error does not show up anymore.
Now you’ve encircled the erroneous child control that causes the error.
Repeat steps 2 to 7 with a smaller amount of controls you remove, until you have only one control left.
In my case it was a user control inside a group control inside a tab control, so I first identified the tab control, then the group control and then the user control.
You could isolate the user control inside a new form to further investigate. In my case it was rather easy; I put checks for design mode around most of the functions inside my control to ensure the code only gets executed if the control is not in design mode.
This fixed my error.
I had the same issue and none of the above answers solved the problem.
At the end, emptying the "bin" folder and rebuild has worked for me.
Let me add two more cases when such exception can happen, along with when control tries to do something that is not allowed under design mode:
When it's impossible to compile the user control.
When designer code contains multiple similar (or identical) lines with initialization of same controls or properties, this can easily happen on merge.
All that cases produce same extremely meaningful error message, and in this particular two debugging of Visual Studio won't help, so I just ended up with bisecting my designer code.
[ReadOnly(true)]
[Browsable(false)]
Above all properties worked for me
After much online research and getting close to what I am looking for by hacking it together (ie. modifying templates and other files, exactly what every expert out there appears to advise against in terms of SharePoint customization) I have decided to go ahead and post my issue here to see if anybody has ever had any experience with this.
In essence, I start off with a plain My Sites host. I would like to keep the My Profile and My Content pages, and add a bunch of new content of top on that. For us, simplicity is of utmost importance and so when I created a new Web Part Page and noticed that it added an additional ribbon under the navigation menu, I decided that it had to go. This is what it looks like out of the box:
With ribbon
Notice that at this point I have already made a few modifications, such as removing the My Site link that by default appears all the way to the left of the other options. This sadly was accomplished in a very brute-force way.
Now, here is the ribbon-free navigation bar, which is just what I want to be able to design without making system changes that I will regret in the future (and that may be easily overwritten by a CU or hotfix)
Without ribbon
So I guess I should make this clear, I don't want the navigation gone, just customized (ie. no My Site string to the left of my options, no Site Actions drop-down for read-only users) and the Browse/Page ribbon that gets added by default everytime you create a new page, well that one just needs to be gone completely, as shown in the second screenshot.
I have read all about hiding ribbons (which just hides the whole thing, including navigation), customizing ribbons (no success in accomplishing this type of basic navigation after trying them out) and simply don't know what to do anymore.
Maybe I am just taking the wrong approach by modifying something instead of just creating it from scratch, at the end of the day it is nothing but a static navigation bar common to all the pages with the special current user drop-down all the way to the right, then if a user has write permissions, she would also get the Site Actions drop-down under Home, that's it.
Hopefully an answer to this question will help others as well who are looking to simplify their SharePoint My Sites host a bit, as out of the box the number of web components that users are presented with might be just a little too overwhelming for your everyday employee, at least in the industry that we operate in.
Anyway, thank you kindly in advance, I look forward to your replies. Do let me know if there is something that is not entirely clear from my explanation :)
If you take away user's Create Personal Site permission (http://technet.microsoft.com/en-us/library/cc262500.aspx) in your User Profile, the "My Site" link will go away.