In Brad Adams' blogged walkthrough of the new RIA goodies, he mentions that you can simply drag a DomainDataSource from the toolbox to your XAML.
All of my RIA kit came from links from that blog and I definitely have the July CTP, yet in my toolbox there is conspicuous absence of DomainDataSource.
What arcane rituals must I undertake to be worthy of toolboxification and the accompanying privileges of automated addition of references to project and XAML?
A helpful Microsoftie responded on another forum. If you right-click the Silverlight controls section of the toolbox for the context menu and add a control you can browse to Silverlight controls and tick DDS in the list. Too easy.
Related
I have created a .NET Core server project that has a lot of classes. I need to generate a class diagram UML, and when I look on the Microsoft documentation site (I think it is only for vs2015), it tells me to click on the "Architecture" menu and click "Add New Diagram", but I couldn't find this button or function anywhere.
Is this function not supported anymore, or have they just not added this function yet? All the forums kept reporting it as a bug, but there's no workaround stated in the forums.
I am open to suggestions. Also I am using VS Enterprise.
Sadly Microsoft removed this functionality in VS 2017.
https://blogs.msdn.microsoft.com/visualstudioalm/2016/10/14/uml-designers-have-been-removed-layer-designer-now-supports-live-architectural-analysis/
Mylyn is a task oriented plugin that allows for example to assign a set of files to a task. Is there a Mylyn type plugin for Visual Studio?
Tasktop has just announced that it is bringing the productivity of Mylyn into Visual Studio! The beta version that is being released will support bringing tasks from HP ALM, Quality Center, and Bugzilla. It includes Mylyn's Task List and Task Editor. The next level of support, which will include compatibility with all existing Mylyn connectors, will be delivered after this beta. Further down the road Tasktop will also be delivering context capture and focus within the Visual Studio IDE.
The beta release will be happening end of November 2010.
See the recent blog post for more details.
David Shepherd, Tasktop Technologies http://www.twitter.com/davidcshepherd
The closest I've found is Tasktop, by the people that created Mylyn, but it's a standalone application that doesn't integrate with Visual Studio.
(Resharper is irrelevant).
Not even close to mylyn, but here is an open source addin for visual studio that helps to assign a list of source files to a "session" (you could think of the session as a "task")
http://dsmaddin.codeplex.com/
i'm not aware of anything open source but i do know that team system is setup to support this type of workflow.
resharper might also have features you are looking for but, again, not foss
I asked that question to the VS.NET Development team in Teched 2008.
She said that they've notice about Mylyn, but are still looking on it.
Task focusing plugin is not yet ready in VS.NET environment.
You may be interested in this news from Tasktop: http://tasktop.com/blog/tasktop/eclipse-mylyn-microsoft-visual-studio
I'll second tasktop. The newest version especially looks nice. Like orip said, it doesn't provide VS integration, but there's a Firefox extension which should be pretty nice... beats using Eclipse purely for Mylyn.
I've recently released (commercial) Task Canvas extension for Visual Studio 2015 that supports tasks with assigned sets of documents and code fragments.
We have an app in progress/development using the Office Fluent UI ribbon control library. It seems that the new RTM release of the Microsoft Ribbon for WPF is going to be the standard for the Microsoft libraries (at least for the next month or so).
Can we install the Microsoft Ribbon for WPF safely on our dev boxes and begin transitioning our WPF xaml to the new control structure while still supporting/running versions of the older Fluent controls?
Can they be referenced in the same project so that we can re-code one window at a time?
The can co-exist on your machine, but they are in the same namespace, so you cannot reference them both in the same project (at least not easily).
The XAML schema is different as well. It's much improved, but you'll have to do a lot of rework of your existing XAML if you've been using the Fluent UI versions.
The VSTO bit I understand. Visual Studio has the project templates to get you started with creating nice .NET based add-ins.
But where is VSTA? I installed the SDK but it seems to be gears towards adding extensibility to your own applications.
I had thought that VSTA was like the new VBA for Office 2007. Infopath 2007 seems to be VSTA enabled but I cannot seem to find where Excel 2007 is also VSTA enabled.
Am I missing something ?
As I understand it, VSTA is not a 'new VBA' nor built into Office 2007, but a separate 'Super-VBA with .NET' that must be licensed from Summit, and distributed as part of an external application. I think it's just targeted at ISVs wishing to extend Office, but the blurb about it also contains this gem:
Perhaps the feature most applauded by enterprise BDMs and SI’s is that VSTA customizations are seamlessly opened by any version of Visual Studio enabling professional developers to continue to enhance applications originally created by end user developers – a feature requested by many enterprises because applications often grow in sophistication over time.
I've not bothered googling BDMs and SI means le Système International d'Unités to me, but I took this mean that you can take the horrible mess of excel VBA that your traders used to turn worthless morgages into goldmine CDOs (and then bailouts), and your 'real developers' can open it in Visual Studio and sort the mess out (or just quit...).
also VBA and VSTA can exist together:
http://blogs.msdn.com/vsta/archive/2006/07/31/684514.aspx
If I understand correctly, VSTA is a new technology that provides a "standard" short-cut route to extensibility for application vendors. So it may appear in Office apps in the future or it may not, but it's not there now.
If it becomes supported by Excel, Word and the like, then the UI (Visual Studio Shell?) should be distributed as part of the package.
But I may be miles off-base...
VSTO 2005 is available to install by itself as a complete development environment
Read more here...
http://msdn.microsoft.com/en-us/library/54ds2za4(v=vs.80).aspx
I am new to developing for Office Forms Server / MOSS 2007. I have to choose between designing my web-based forms and writing code for them in Visual Studio Tools for Applications (aka VSTA) or Visual Studio Tools for Office (aka VSTO). VSTA is included free as part of the license for InfoPath 2007; VSTO, also free, requires Visual Studio 2005 / 2008. I have licenses for both of the products and cannot easily decide what the pros and cons of each IDE might be.
This explains it better than I can: http://blogs.msdn.com/andreww/archive/2006/02/21/536179.aspx
Given the fact that the license for VSTA comes with InfoPath, I'd probably run with that.
To add to Bennor's answer I would avoid writing code "behind" InfoPath forms entirely. This is a desperate attempt to make 'dumb XML' as much as possible instead of "smart" XML that is entangled with code. Failing this, my next choice is VSTA because historically these solutions (at least the ones I have written) have a lower security risk and can run on more diverse Office environments.
The last resort is to use VSTO. This is my bias... most of my VSTO investments are in Microsoft Word.