In the document "Microsoft Ribbon for WPF October 2010 Update Release Notes" (WPFRibbonOctober2010-ReleaseNotes.rtf) , it states the following:
System Requirements for Installing Microsoft Ribbon for WPF
...
Supported Architectures:
x86
x64 (WPF Ribbon is only provided in x86, however, the components will install and function properly on x64 operating systems)
Regarding the significance of the final bullet - what specifically is provided only in x86? For a .NET library this seems a little odd, maybe there are some unmanaged DLLs also?
This could be relevant in a deployment scenario and I just find the wording somewhat vague.
Thanks
Related
I have multiple DLLs of a WinForms control targeted for different versions of .NET Framework and need to add them all in a Visual Studio Toolbox while showing only the one which is most suitable for currently selected version of .NET.
The control have different features when compiled against different versions of .NET, this is why it would be best to show the most "native" version only. For example, the control have some features removed in .NET 4.0 Client Profile or makes use of .NET 3.0 features when available (not avaiable in .NET 2.0).
The problem is that the control have same name and is signed with same Strong Name Key (SNK).
I can modify source code, but what to do to enable all versions of the component to reside in VS Toolbox?
We are using prism for developing WPF applications. The newest(4.1) version supports only windows 7 and windows server 2008 as per the following link
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=28950
This begs a question. As far as I know specific operating system support is only required for assemblies with legacy code. If the assembly is completely written in .NET it just need the .NET frame work support as this itself is a "virtual machine".
If this is true is prism contains legacy code?
The Prism 4.1 Deveoper's Guide provided here says the following:
This guidance was designed to run on the Microsoft Windows 7, Windows Vista, or Windows Server 2008 operating system. This version has been smoke tested on Windows XP Professional and Windows Server 2003, but it has not been exhaustively tested. WPF applications built using this guidance require the .NET Framework 4.0 and Silverlight applications require Silverlight 5.
All this means is that they haven't tested it on XP, but you needed XP SP 3 and above for the last release (the minimum for .NET 4.0), so my guess is it will likely work for new projects.
No need to panic.
It is possible to include a visual c++ 2005 .lib in a Silverlight project?
I wrote an ActiveX that includes a library written in visual c++ 2005, and now I want create a Silverlight plugin for cross-browser portability.
Unfortunately the only managed runtimes supported by silverlight is c# and Vb.net so no c++ :-(.
Silverlight will however support PInvoke in version 5 but there are some tricks to it that might not fit with your usecase. It does however require elevated trust.
Probably not, Silverlight is very limited. But with the release of Silverlight 5 there seems to be support for PInvoke.
http://www.microsoft.com/silverlight/future/ Quite a bit down on the page.
Silverlight 5 is released later this year.
I have been using WPF for some time now and I am trying to reproduce some of the nifty UI features of their office suite. Although very easy in WPF, I am wondering how it could be done using MFC feature packs (I might have to use it instead, since my company has not yet approved the use of WPF). Since the Fluent UI was introduced with Office 2007, I am wondering if Microsoft actually uses WPF in anything else than VS2010 or Expression Blend and particularly in Office 2010.
I hope that this question is not off topic.
Office 2010 does not use WPF. In fact, it doesn't use MFC either. Office has traditionally used a custom UI toolkit, and this was true even before the Ribbon came into being. However, you only need one major first-party application to secure the viability of WPF as a UI platform. This is especially true when that application happens to be Visual Studio, since tens of thousands of Microsoft employees use Visual Studio every day.
But that doesn't mean that WPF is the best UI technology to use with the Ribbon. The Microsoft WPF Ribbon handles a lot of corner cases incorrectly, as do all the major commercial managed-code Ribbons that I've tested (WPF or Winforms). It is very hard to duplicate the Office Ribbon -- there are a lot of subtleties that are difficult to anticipate and only turn up when users run into corner cases.
The Office Ribbon took over 200 man-years of work and was exercised by tens of thousands of beta testers. (Jensen Harris estimated at UX09 that the Office UI team numbered some 15 PMs, 30 developers, 30 testers, along with half a dozen designers and UI researchers.) It's the best-tested Ribbon out there, but unfortunately it's one that developers outside Microsoft can't use.
The second most reliable ribbon framework is probably the Windows 7 ribbon, which is used by Paint and WordPad. This one is available in the Windows 7 SDK, and has been backported to Vista. Native code and GDI, so it's targeted towards C++ developers. Note that it's also not tied into MFC.
As far as I know it does not use WPF in any way. In fact much of it is still written in C++. Really the only "big" applications Microsoft has released in WPF are Visual Studio 2010 and Expression Blend.
You do realize WPF (with the .NET framework) is just a layer over win32 and com (direct2d, etc), all of which can be accessed from plain old C++, not to mention MFC. They already had all their ribbon code in C++ from 2007, so making the 2010 interface isn't hard.
To answer the question you think you're asking, no, Office doesn't use WPF. Only Visual Studio uses it.
I have some code which is in Silverlight 3. I am unable to move to SL4 at this time.
I would however like to use VS 2010 to do my SL 3 development... and SL4 development.
The idea of both runtimes coexisting on 1 machine i thought I heard Microsoft got
right this time in VS 2010.
is this correct?
if yes, then Where can I find the instructions how to set this up?
thanks for any help you can provide,
Sincerely,
J
Silverlight is not side-by-side. VS 2010 provides multi-targeting support for the full .NET framework, which is side-by-side, but NOT Silverlight.
There can only be one version of the Silverlight plugin and runtime on the machine.
That said, if you want to build code targeting one or the other, that is possible by checking in the Silverlight versions to your source enlistment. This post is a little outdated but provides an example for doing this for SL2 and SL3.