I'm working on a program and I had this problem:
when I add a button, for example, it's called automaticly button1, button2, etc.
I want the posibility to name it as I want it to be called right when I add it without the need of changing the 'Name' in the properties. Like you add a new Form and can name it as I you want, like that just for button, textboxes, etc.
Thanks
You should look into the Visual Studio 2010 Visualization and Modeling SDK. It answers your need, here is Microsoft introduction to it on MSDN
Domain Specific Languages (DSL Tools) and Architecture Tools SDK for Microsoft > Visual Studio 2010. This SDK provides tools and templates for building Visual > Studio Domain Specific Language designers for Visual Studio 2010 and extending > UML and Layer designers. By using this SDK, you can build your own graphical
or form-based designers for Visual Studio 2010 and extend existing tools.
Related
I could not find how to generate existing class diagrams on VS2017 Community Edition. Is it not available to Community Editions. Could you please help how can I generate class diagrams of the project?
I assume you mean class diagrams, not UML diagrams.
Starting with Visual Studio 2017, the support for class diagrams is not installed by default. You need to explicitly select it during installation:
From the Start menu, launch Visual Studio Installer.
Click Modify button for your installation.
Switch to Individual components tab, scroll down and select Class Designer. Press Modify button.
The complete procedure with screenshots is described here (because our product VSdocman also relies on this feature if you want to generate class documentation with the diagrams).
I have the impression that you're not talking about the UML diagram feature which was retired indeed. I'm assuming you're talking about the Class Diagram.
First of all as Peter pointed out, make sure this feature is installed in your system.
Then, as answered here, it's a known issue (VOTE!)
As a workaround, From the New File dialog box create a plain XML named Diagram.cd (replace Diagram with your choice), right click the file and select Open With..., and select XML (Text) Editor, then replace its contents with the following:
<?xml version="1.0" encoding="utf-8" ?>
<ClassDiagram MajorVersion="1" MinorVersion="1">
<Font Name="Segoe UI" Size="9" />
</ClassDiagram>
Then close the file saving it. When you reopen it normally it should work now.
Community edition doesn't allow you to do it.
Version support for VS 2015 for architecture and modeling tools
Apparently Microsoft has decided to not add that functionality in Visual Studio 2017, for any of the product versions
blogs.msdn.microsoft.com
I installed C# and business intelligence inside visual studio 2010 and now I'm able to access/create BI projects but can't findout anything under Visual C# template "no item found"
In visual studio project creation form -> choose Visual C# and choose Installed Templates.
You see no item found cause most probably you have selected Online Templates.
I would like to make a UML flow diagram and I currently have Visual studio 2013 however I cannot find a way to begin creating a UML Diagram i.e. either the project to add or the item.
I cannot find the 'Architecture Menu' and there doesnt seem to be a way to add it.
Any Ideas on what I'm missing / Doing wrong?
This is the type of diagram I would like to create:
You require the Visual Studio 2013 Ultimate SKU to access the modeling features. To check which version of Visual Studio you have click on Help > About Microsoft Visual Studio.
You can compare the features available across various SKUs here: http://www.visualstudio.com/products/compare-visual-studio-products-vs
A major part of our work is creating and manipulating certain XML files, for which have a custom editor. The editor is starting to get creaky and we are looking at building a replacement. Since VS2010 has recently arrived, ostensibly with an improved add-in architecture (MEF?), I am interested in the possibility of building the editor as a custom editor within Visual Studio.
It would have to appear in the same way as the code editor or the Designer - a tab item, of which there can be many open at once, containing the GUI we use to edit the files. It would integrate with VS's Edit menu. It could use the output window to display messages. It would appear the same as any other editor within Visual Studio.
Right now, I am looking for examples of add-ins that work in a similar way - ideally with source code - to see whether this model would suit our requirements. I am also looking for any documentation or tutorials relevant to creating a VS2010 add-in, or information about VS2008 add-ins if this is still relevant.
Any input is welcome. Thanks!
You want to look at the Managed Extensibility Framework for VS 2010. Since 2010 is written in .net you can create add on components using it.
Code editor extension for VS 2010.
Working with MEF
Custom Editor Extensions
Update:
Since someone asked in a comment, I thought I would post this link on creating add ons for vs 2008: http://msdn.microsoft.com/en-us/vstudio/bb968855.aspx
i want to convert my window application, that i developed in VS2005 using C#, as an Add in for Visual Studio 2005. How can i do it.?
There is a nice quick start tutorial in here : http://www.codeproject.com/KB/macros/LineCounterAddin.aspx
It was enough for me to start.
You could try looking at MSDN or books, but you might find the VS2005 information hidden behind the VS2008 stuff...
I wanted to create one myself, but i didn't have yet time to process the information required:
"How Do I?" Visual Studio extensibility videos
Article series detailing extending visual studio from the beginning:
LearnVSXNow!
Microsofts's VSX
Home on Code Gallery
Building your own Visual Studio Source Code Outliner extension (and Quan's whole blog)
Overall I'd recommend waiting for Visual Studio 2010 (or start working with the fresh beta 1), because there will be many changes and many more possibilities on extending Visual Studio. (Think WPF.) The code gallery I linked already contains content regarding to this.