I am using VS2015 and am connected to my TFS. However when i click Team Explorer/Builds, the "New Build Definition" button does not show up. The strange thing is this all works in VS2013. Is there a toolkit i am possibly missing or is the button hidden? Not sure what i could be overlooking for the button to not show up in one version and show up in the other...
Open page Team Foundation Server in browser. And open your project. And find tab Build.
You need to update the application VS2015.
Or open in VS TeamExplorer then Builds and:
Build Definitions -> Actions -> Security...
and configure security access control.
Make sure you have expanded the Build Definitions by clicking the triangle:
Am using VisualStudio 2013, update2. I am facing the below issue when I opened a project in VisualStudio today, I noticed on right clicking a project in the SolutionExplorer the context menu have a lot of options that even have scrolling now. Now I have to scroll down everytime to build or clean a project.
Earlier it was like a short menu like below.
I have not changed any settings but don't know why am facing this issue. I tried to customize the context menu command and chose (Project and solution context menus | Project) from the drop down, but that didn't worked out as it is automatically reset to tfs on clicking the close button. Does any one have idea about how to rectify this?
Note: The context menu has changed only for the projects inside the solution. On right clicking the solution name in solution explorer, I am still getting the same old menu.
From looking at your context menu screenshot, it looks like you have some extensions installed that have introduced these commands. Try disabling some or all of them in Tools > Extensions and Updates Manager to see which ones belong to which extension. There unfortunately isn't a way right now to customize this context menu.
Thanks,
Cathy
Visual Studio IDE Team
I'm unclear on what makes a project in visual studio "right click publishable", does anyone have an idea/information on this?
I realize that project types such as console apps, web apps, etc should be right click publishable. However, I'm struggling with figuring out what makes a class library right click publishable. I have several class libraries that I've created that don't have "publish" available as an option when right clicking the project file in visual studio, however I have happened across a class library project from another developer that has the option to right click publish.
What/where is the right click publish option configured on a project?
When I drag controls from the toolbox to an .aspx page or the designer for that page nothing shows up. I am using Visual Studio 2010 with an existing website project.
** Update
It seems to work now... I'm not sure if this was specific to one project, or a combination of things.
Is the project under source control or in a read only state?
I think the project is so messed up it just doesn't work. If I start a new project it works, so I'm going to leave it at that
As stated in the title, I copied my DLL in Visual Studio project, set it to "content" and "copy always". Added a reference to this DLL and set it to "copy locally".
I successfully managed to instance my component to a form through code but it doesn't appear in the toolbox, really boring.
How can I solve this issue?
If I link directly the DLL project to this project it works, but now I'm treating the DLL as "external" so it's not part of the same solution of the DLL project.
I had this problem with #AndrewFinnell's solution:
There are no components in 'c:....\XXXX.dll' that can be placed on the toolbox.
So I solved with drag and drop:
open Windows explorer and navigate to the DLL
drag the DLL and drop it on Visual Studio in the Toolbox, exactly where you want your components to appear.
I also realized that some components may have compatibility issues with certain .NET Framework versions. For instance A Professional Calendar/Agenda View That You Will Use seems not to work with .NET 4.5, while it does with .NET 4.
Right-click in the toolbox.
Click "Choose Items..."
Click "Browse..."
Navigate to your DLL and click Open
Then click "Ok"
Your components should then show up
The way I found to make this working is:
Add the dll, reference it
Compile the project
Save the solution and restart visual studio
And then controls show up in toolbox (not always working, I think is a sort of visual studio bug)
Like said above,
I reference the DLL in the client project by: in Solution Explorer right click > Add Reference, at this time the custom control doesn't appear in the Toolbox.
I save it and close the client project.
I restart Visual Studio 2012 and reopen the client project. Now the custom control is in the Toolbox.
I reopen the custom control project, make some modifications and compile.
And the most important, all changes that I made in the DLL project automatically were updated in the client project without need to redo "Add Reference".
Here is what I did.
After install the net 3.5 chart download from MSDN link, I manually copied the 3.5 chart dlls to my project and refer to them. Then, from the "choose item" of toolbox, browse to the dlls and add them into toolbox. Make sure the checkbox is checked for the "chart" in the "choose item" popup.
After these, the "chart" item in the toolbox should be available and enabled for .NET 3.5 project.
NOTE
(I am using Visual Studio 2010. I think my solution should work for 2012.)
I was having this same issue. I am working in Visual Studio 2010.
My user control library is written in C# and my project I'am importing it into is in Visual Basic.
If I had the C# project in my solution, the custom user controls would show up automatically. But if I only referenced the DLL it would not load the custom user controls from the referenced library into the "Toolbox".
The above post that mentions finding the file in explorer and dragging and dropping it into the toolbox solved the problem. This is a very strange way of behaving. VB user control libraries don't require this step.
This has been an issue I have had sitting on the burner for the last 2 years.
I would up-vote the previous answer but I don't have enough rep yet.
This post could use some better tags, cause it was buried on most of my google searches.
So
Reference the user control library
Drop the DLL file into the tool box.
One question I have in regards to this is: what happens if you change the project reference to the DLL (because it moved) and not attempt to update the toolbox reference (by removing the control from the toolbox and dragging and dropping the DLL from the new location)?
I tried following the other answers (thanks to all of you!), but I got this problem and I'll let you all know how I solved it and show my custom tools in toolbar (in VS 2017).
Place the .ddl file in any Library Solution
Then I add that .ddl as reference to my needed project
Build the project and restart the Visual Studio
Then, when I look into toolbox, my custom toolbox name appears in
toolbar, when I expand that I got below message
There are no Usable controls in this group. Drag an item onto this
text to add in to toolbok
I dragged the .dll and dropped under that text and then all my custom tools appeared in my toolbox.
And add lib. to folder in your solution example solutionfolder/bin/debug and then add reference to object from this folder, finally rebuild, quit, come back, drag and drop dll from this solutionfolder/.../../ and it will probably appear.