My company has made an Entity Framework model of the database with all of the relationships mapped out and I'd like to take a screenshots of that with all of the FKs included in it. But I can't seem to figure out how to take a screenshot that includes all of that information. Any advice?
The "Export as Image" feature of Entity Framework generates an image that is too pixelated.
Alternatively, use NClass to generate diagram from ur Assembly containing EDMX classes
An alternative if you have Office OneNote 2007 you can simply print it to "Send To OneNote 2007" printer. Then you can use your favorite image editing tool to cut it however you want.
Oh the joy of Visio not being a major player in this game anymore. you can still reverse engineer a DB using Visio - which gives a nice presentation for printing.
Personally, the VS 2010 Entity viewer (Server explorer) is the easiest and quickest for me to use. The presentation isn't that bad either. Though you have more options with Visio as far as printing and portability. (You can still do Viso -> SQL in Visio 2010 with an addon).
Snipping tool (Vista/Windows 7) Start->Programs->Applications->Snipping it is such a helpful tool.
And oh am I glad no one actually said: "use your iPhone, take a picture and text it to your boss".
Why don't you use the Microsoft SQL Server Management (Express) Studio Diagram Option?
(To display the names of your relationships you can use Database diagram -> Show releationship labels)
Or you can use Ctrl + the mousewheel to scroll in/out in Visual Studio and you the Snipping Tool to take a screenshot.
Related
I am looking for free extension that has one simple functionality which is sidebar file navigation like is in SuperCharger or Resharper (see attached screenshots). Sadly both of them are paid :-( Does anyone have a good alternative?
Visual studio has Class View window for a quite a while.
You can try Productivity Power Tools, with it, you can:
Expand code files to navigate to its classes, expand classes to navigate to their members, and so on (C# and VB only)
Search your solution, all the way down to class members
Filter your solution or projects to see just opened files, unsaved files, and so on
View related information about classes and members (such as references or callers/callees for C#)
Preview images by hovering over them, or preview rich information by hovering over code items
We've also added support for multiple selection and drag & drop.
https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.ProductivityPowerTools
I know its an old question, but as i was looking for an alternative to supercharger // Resharper (for the navigation only) few days ago, and had looked on stack before doing my search (and as I found the answers not exactly what i was looking for) ...
After testing a few extensions I finally found a good alternative to those two paid solutions :
https://github.com/sboulema/CodeNav/blob/master/README.md
You can also just download it from the extensions menu , search for CodeNav .
Best.
I just signed up on this site because I think here are the most qualified people for answering my questions. Maybe someday I can answer some too :)
<p>Hello, Stackoverflow!</p>
Here is my question:
There are many beautiful IDE's like Atom or Sublimetext where you can adjust your window layer just like you want. Now, i find trouble in Visual Studio doing this.
Here is a preview how it should look like (Atom)
This is my favourite layout and i want this to be in VS
So, is it possible? Maybe with an extension or even a built in function?
When entering a work item in TFS2010, it's often nice to refer to other tickets in the text free fields (either description or Acceptance Criteria field).
Most other ticket tracking software I have used automatically creates links/hyperlinks to other tickets if you put appropriate text into these fields (e.g, Trac, BugTracker.NET, etc).
I understand the link tab, and that you can create relationships there, but it would be lovely to have this feature available and clickable in the other text field.
Does TFS2010 (+ Visual Studio 2010) support something like this? I cannot find for the life of me, a solution.
If you use a rich text edit field (the advanced text field available for work item definitions, with coloring buttons and so on), you can include hyperlinks, also to other workitems etc. This is however a manual exercise to make the hyperlink point to the correct item, there is no automatic recognition of #-tags or whatever to refer to other workitems.
Hi you could use a plugin called TFS Extensions Kit. TEK workitem. This is a Visual Studio extension that allows, besides other features, to open, in Visual Studio, workitems and queries from a Hyperlink.
So you could use the hyperlinks in any field.
Look at the Visual Studio Gallery:TFS Extensions Kit. TEK workitem
You can download a demo from here
Regrads
It's an old question, but if you get here looking for the answer for VSTS the answer is hashtag followed by itemId. Similar to #UserName to reference another user.
Eg. In comments box typing This is a dupe of #2428 will translate into This is a dupe of User Story 2428: Story name where User Story 2428: Story name is a link to the item.
I would like to add a button to the Ribbon and have it perform some basic tasks when clicked. Is this possible? If so, how?
Thanks in advance.
No, it is not possible. It looks like it is possible, but it is not. The only proper add in for Excel 2011 Mac is provided with Excel, and the ability to show it in Excel Mac's ribbon is apparently hard-coded into the Excel Mac application. None of the XML-based techniques for extending the Excel Mac ribbon work because the ribbon is hard-coded. It looks like the Windows version, but it is nothing like it.
Obviously, it is hard to provide sources for a negative answer. I have researched this topic carefully including contacting Microsoft support, and found that there is no compiler or IDE from Microsoft for this purpose. You can certainly develop in VBA in Excel Mac, and you can make an XLA add-in, but you cannot access the ribbon. You can create little square Mac toolbar icons, just as in Excel 98.
Here are some useful links that will answer your question:
how to customize the ribbon
how to customize the ribbon with vba
how to create an add in (on MSDN)
a clearer tuto on how to create an addin
Please ask a more precise question if you want more precise help.
We're working on creating a specialized graphical editor for our enterprise applications. We've looked at and rejected DSLs. Ideally I'd like to have the main interface of the editor be docked like the code windows and use WPF for drawing. Can anyone point me to some documentation to get me on the right path?
Thanks.
Colin.
UPDATE: It's beginning to look like "no." From http://msdn.microsoft.com/en-us/library/bb166228.aspx: "Document windows are created by implementing an editor. The IVsEditorFactory interface creates document windows as part of instantiating an editor. For more information, see Accessing the Editor By Using Legacy Interfaces."
Following the link to http://msdn.microsoft.com/en-us/library/dd885127.aspx gives this this bit of advice: "You can access the Visual Studio editor from legacy interfaces. The Visual Studio SDK includes adapters known as shims, which enable these interfaces to interact with the new editor. Nevertheless, we recommend that you update your legacy code to use the new editor API. Your code will perform better and you can use new technologies such as the Windows Presentation Foundation (WPF) and the Managed Extensibility Framework (MEF)."
So, to sum up: if you want to implement an editor you have to use the legacy interfaces, but you shouldn't use the legacy interfaces because then you can't use WPF or MEF.
Seriously Microsoft, WTF?
UPDATE 2: Now that I have the proper names ("custom editor"), I was able to find the following topic: http://social.msdn.microsoft.com/Forums/en-US/vsxprerelease/thread/9e605d0f-1296-47c9-a534-e54905251ebe
I still don't see why they couldn't have included that somewhere prominent in the MSDN docs. You know, like somewhere near where they tell you that you can't use WPF if you're using the legacy interfaces.
Creating a custom editor doesn't have to be terribly painful. Yes, a custom editor will require implementing a few interfaces, but you can still use WPF to actually create the control that is hosted in the VS document frame.
DiveDeeper's blog has some great resources for learning about creating a custom editor.
Creating a simple custom editor - the basics
Creating a simple custom editor - the first 10 meters
Creating a simple custom editor - under pressure
I'd recommend using a library like VSXtra to do a lot of the work for you. It will provide you with a nice base implementation of an editor factory, editor pane, package, etc. Istvan Novak writes about building a custom editor with his VSXtra library in this blog post.