Does anyone know of a way to move a UML diagram from one Visual Studio 2010 project to another? I have two modeling projects that I'm trying to consolidate, but I'm not having much luck. It looks like only the XMI import functionality is included in Visual Studio 2010 Feature Pack 2.
Davester, you'll find a similar question that was answered on the VS Visualization & Modeling Tools forum:
How can we import an existing *.usecasediagram file?
Basically, you have to copy over all the elements from the diagram in the source project over to a diagram in the destination project. The diagram files themselves belong to their parent modeling project and must be opened from that project.
Related
In every tutorial and HowTo site (like here) about WiX I read I should add reference to my other project, but when I select Add Reference I have nothing on Project list in Project tab. I try this on Visual Studio 2012, earlier with WiX 3.7 and now on 3.8.
If there is solution simply not using "Add Reference" function how can I build this other way? I'm a beginner so I don't really know how to use WiX without this feature, if I published my C# application in Publish Wizard I should add all produced files to Component Group with every file in <Component> tag?
It could be this simple...
In Visual Studio, Add Reference's Project tab only lists projects in the same solution. You just need to Add Project to the solution and go back to the Add Reference's dialog.
A solution is just a set of zero or more projects that can be built together. You can have a project in more than one solution. The only limitation is that if project B references project A (B is downstream of A), A should be in every solution that contains B. If the universe of projects is small, it is typical to have only one solution for them all. On the other hand, if one developer works only on upstream projects, that developer might find it easier to work with a solution that doesn't have downstream projects.
Setup projects tend to be downstream but note that they probably don't depend on library test projects.
[Stream is not the best technical term. The universe of connected projects is a directed acyclic graph.]
My project team is currently working on a modelling project for a mid-sized piece of software with Visual Studio 2010. We are using AnkhSVN for source control.
We are not editing files concurrently, we only edit different files in the same project.
Sadly, after each commit, there are a lot of conflicts in a file with the ending .uml, located in a folder with the name ModelDefinition. This file seems to be changed whenever any diagramm in the whole solution is changed.
If we put this file on the SVN ignore list, so we can work on the modelling project concurrently, all files in the subversion are displayed as blank files.
Is there a way aroud this dilemma, so we can edit our modelling project simultaneously by using SVN?
MSDN has instructions for sharing modeling projects. Basically, you have to organize the modelling elements into packages in the UML Model Explorer. If you put the elements into different packages, they will also be put in different .uml files.
The quickest way I've found to reorganize an existing diagram is to create a new package in the Model Explorer, set the Linked Package property of the diagram you want to move to the new package, select everything in the diagram, copy it, delete it, and paste it again.
Can someone briefly explain to me the difference between Visual Studio's solution file (.sln) and project file (.vcproj).
It seems to me opening either one open the correct solution/project in Visual Studio. Is one the super-set of the other?
Note: I am currently using Visual Studio 2008 working on a project that was brought forward from Visual Studio 2005 (I believe).
A solution is a set of projects. If you need more than one project in your software, then go with solutions. I.E.: A Class Library Project + A Web Application Project.
A project file typically corresponds to a single module: EXE or DLL or LIB. A solution manages a collection of project files.
A solution is a collection of projects. Visual Studio is made so that it cannot function without a solution, so if you open a bare project, it will generate the solution automatically (or try to find one).
One solution can contain zero or more projects. Everything is in projects, so a solution with zero projects doesn't contain anything at all besides the solution properties.
Visual studio keeps track of where the projects are used, so if you open a project file, it will open (IIRC) the last solution where it was used.
When you create a project from scratch, a solution is also created, but it's not shown until you add another project to it. It looks like you have only the project open, but it's actually a solution containing the project that is open.
Specifically project files are intended to contain the data required to build the files in the project into an exe or dll. This file is utilized by the local compilers or with systems such as Team Foundation system and server side build agents.
Solutions are a client (IDE) construct designed to manage collections of projects, which in effect is a collection of different build definitions and associated files.
Solution files are typically made up of multiple project files.
I have successfully managed to create Visual Studio starter kits in the past, however as far as I am aware they can only be made at the project level.
I have a solution that contains multiple projects that I want to distribute throughout an organisation for several software projects.
The starter kit that I want to make is at the solution level, and contains multiple visual studio projects, that are clearly seperated, ( e.g. seperate code and test projects).
Does Visual Studio 2008 support this, and if so how is it done ?
I found the solution here http://msdn.microsoft.com/en-us/library/ms364046(VS.80).aspx#creatstrtkt_topic3
Instead of deleteing this I thougt that it would be useful reference for someone else.
I want certain projects in my solution opened in Visual Studio have different icons..Just like how Visual Studio displays different icons for class project, web site project etc
I am not talking about changing the icon of the winforms or other such app being produced
I understand I should arrange my code into proper namespaces / folder structure...and can even arrange the project into solution folders...but above will communicate better to my teammate for time being...(unfortunately we have inherited a reasonable code base and things needs to be cleaned along further development)
If you look in your SLN file, the project has a guid assigned to it.
all the c# projects have
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}")
and all the build folders have ..
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}")
These define the project type, which you can hunt down in your registry ....
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Projects
With this finding, I would say what you are looking for is VERY possible, but you'll have to create custom project types for visual studio. This may not be as daunting as it sounds, if you start with on of the default packages.
Here is a pointer to a sample, where in fact they mention setting the custom icon in step 3.
Building a Custom Project Wizard in Visual Studio .NET