I have just installed MonoDevelop 2.0 on Windows and created a New GTK Project.
I can't seem to find any way to open the GUI Designer (there are no 'Source Code' and 'Design' tabs under the codument either).
How do I open/use the GUI Designer in MonoDevelop?
I recently installed MonoDevelop 3.0.6 and ran into this problem as well. I created a new solution, selected VBNet and Gtk# 2.0 Project. I then opened the MyWindow.vb file and there was no tabs at the bottom for selecting Souce Code or Design. Also the Toolbox was empty.
I then tried creating a solution using C# and GtK# and when I opened MainWindow.cs the Designer tab and Source tabs show up at the bottom of the window. Here are the instructions for it's use http://monodevelop.com/Stetic_GUI_Designer.
Update: As per the Bugzilla Bug 10986, GTK# Designer only works with C# Projects.
First of all, you need to create a GTK+ Project which allows you to use the GUI designer. After doing this, user interface references will be automatically loaded and a skeleton MainWindow code file will be automatically generated by the IDE itself. If you click on this MainWindow code file from the solution pad, 'Source' and 'Designer' tabs will appear at the bottom. Finally, just click on Designer tab and now you can see your application main window and GTK+ widgets in the toolbox.
Related
Does anyone else have this issue? There does not seem to be a way to edit the Solution Explorer toolbar. One of the icons for Solution Explorer is missing in my C# projects.
I am using Version 16.10.3.
I managed to add this icon to the wrong place, but maybe you can find the right place and update this answer.
I did this by customizing menus:
Clicking Tools | Customize...
Selecting Commands tab
Clicking Add Command...
Selecting View
Selecting View Code, and then OK
It looks like what you have to do is find the right place to add it in the first place.
The options under Commands are Menu bar, Toolbar, and Context menu, none of which seems to fit. I looked around briefly; maybe you can do a more in depth search to find the right spot.
I have several extensions installed. One of these modifies the Solution Explorer behavior for dynamic nodes. It's possible that extension or another is interfering with this icon. Try also disabling your extensions and see if that has an effect.
Folks, I figured out the issue. When you create a .NET Core 5.0 project the VS environment is setup different. I deleted the .NET 5.0 project and recreated as a .NET Standard one with the same name and the icon showed up again.
In fact, the Studio 'solution' version is different although your using the exact same VS application. Problem solved for now.
In Visual Studio versions prior to VS2019, .NET framework 4.7.2, if you wanted to design a MenuStrip, you just added the MenuStrip to the form and start typing the ToolStripMenuItems. Like this:
I've recently moved to VS2019, and started to use .NET 5. If I add a Menustrip, I get an empty strip, which seems not easy to edit (I colored the background of the main form, to clearly see the white menu strip)
My question is: how to add ToolStripMenuItems?
I see the little arrow on the right, and I can select Edit Items, but to add a menu that way is quite cumbersome.
If I open an old solution in VS2019, I can edit the menu as I used to do. So it's not VS2019.
If I create a new VS2019 project using an old .NET version, I can't edit the menu, so it's not the .NET version
If I copy paste InitializeComponents from an old project to a new .NET 5.0 VS209 solution I cannot edit the menu
So, how to edit the menu? Is edit items really the proper method to edit your menus from now on?
I believe that the MenuStrip editor experience difference comes down to .NET Core vs .NET Framework.
Edit: .NET 5 = .NET Core vNext
We covered MenuStrips while we were doing WinForms in my C# class and this exact question came up. .NET Framework solutions allow you to use the convenient editor as you have demonstrated. .NET Core solutions do not.
The easiest way I found to build out my MenuStrip items when in .NET Core was to click on the menu strip, then there is a property called "Items" which is a collection. In the properties pane, you can click the three dots button to bring up the Items Collection Editor:
Here you can create new ToolStripMenuItem objects to build your menu.
Possibly related post, others suggesting this is a Core vs Framework issue: MenuStrip not allowing to create menu
This issue has been fixed
in Visual Studio latest release v16.10: 05/25/2021 (https://learn.microsoft.com/en-us/visualstudio/releases/2019/release-notes). I have tested this both in net 5 (current) and net core 3.1 (LTS).
Demo:
https://youtu.be/3s55hWrHx4U
You might have used the option that says "Windows Forms App."
This is wrong. You should use "Windows Forms App(.NET Framework)." This will let you edit the menuStrip control the easy way.
I have made several controls over the past time through Folder > Add > User Control, then dragging an ObjectListview onto the designer and setting anchor/ dock etc then implementing the code.
Since this morning when drag an Objectlistview onto a control, it shows up as a component in the bottom tray instead of on the control's design canvas.
I can't remember installing any updates on either visual studio or the ObjectListview NuGet package, it's still 2.9.5 from 2017. The behaviour is the same in Visual Studio 2017 and 2019 preview..
I did install .Net Core SDK 2.2.402 ealier this week but this project references Framework 4.6.1..
When I add a standard TreeView or ListView etc onto the form they get added normally.
I'm comparing the code with other controls I created this way, both derive from UserControl. The control that works as normal has the line near the end of InitializeComponent()
this.Controls.Add(this.objectListView1);
For some reason for new controls I create that line isn't generated by the designer for ObjectListview.
If I manually add that line to InitializeComponent() the control does show up on the design canvas but I can't select it or do anything with it.
Does anyone have any idea what could cause this changed behaviour and how to fix this? I'm working sundays b/c I'm very busy this is really messing me up.
I was able to fix by uninstalling and reinstalling the nuget package.
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.