xbap

I'm looking into creating a system / site which includes a website. I would like to get the benefits of WPF, and WBA seems to be a good avenue of doing this. Silverlight on the other hand is also good for accomplishing this goal, with the difference that WBA provides more options and power than Silverlight. What are the benefits / losses that come with using WBA versus Silverlight? Is WBA only supported in IE? Any insight would be very helpful. I assume you mean XBAP (XAML Browser Application) with WBA? Silverlight and XBAP are pretty similar to each other but they do have some major

I did the following steps to deploy my wpf application that need full trust permission: 1-Creating a certificate using makecert.exe 2-Creating signed application and deployment manifests. 3-Building a website in IIS to host files (include MyApplication.exe.manifest and MyAppicatio.xbap) 4-Adding certificate - used to sign manifests - to IE certificate store (Trustes Root Certification Authorities and Trusted Publishers) , IE Menu bar->Tools Internet Options->Content->Certificates But when i try to browse Xbap file in IE6 it throws Not granted exception for dowloading MyApplication.exe.manifest

I have a WPF application and there is a Datagrid in some pages. This datagrid needs to load 5000 rows at once (Pagination is not an option for me) and this takes ages. I set EnableRowVirtualization=True and the performance is acceptable now, but there is a problem here. In my datagrid I need to set different background colors to different rows depending on a column value (say STATUS), changing EnableRowVirtualization from False to True, caused incorrect coloring when I scroll. ----Edit---- Here is my XAML code: <my:DataGrid Name="dgDataGrid" DockPanel.Dock="Top" AutoGenerateColumns="False"

My XBAP application uses two win32 dlls and as usual many .Net dlls. Since we add .net references to the project itself, that is not a problem, as they all get deployed automatically when publishing the project; only that their names change from mydotnet.dll to mydotnet.dll.deploy . But the problem is, the win32 dlls don't get deployed, neither their names change. And I understand the reason. It's because I call them using p/invoke techniques, and they're not added to the project. In fact, visual studio 2010 doesn't let me add them to the references. So I manually copied them to the publish

I'm developing a .NET 3.5 XBAP application that runs perfectly fine in FF3 and IE6/7 etc. I'm just wondering if its possible to get these to run under other browsers, specifically (as its in the limelight at the moment) Google Chrome. XBAP applications do work in google chrome, however you have to set your environments PATH variable to the directory where xpcom.dll is located. for example SET PATH=PATH;"C:\Program Files\Mozilla Firefox" At the moment, XBAPs do not work in Google Chrome. I've gotten it to run once, somehow, but every time there after I've received an error that the browser

I've made a WPF Browser Application that hosts old WinForms controls (I haven't migrated fully to WPF yet). Using WindowsFormsHost means my Browser App requires Full Trust to run. This is not a problem for me since this app is only meant to be run on the intranet at my company. However, after I deploy the xbap to a network share, it refuses to run, saying "Trust not granted". What are the methods I can use to grant Full Trust to XBAP applications stored on my companies intranet? So far, I've found 2 ways to do this. Through a really complicated method of installing certificates on the target

I'm pretty familiar with a lot of the ins and outs of full fledged WPF client applications. I know that WPF client applications supports the full .NET Framework 3.5, allows for hardware acceleration of 2D and 3D graphics, theming, templating, styling, triggers, the works. What I'm not clear about is what features, and/or niceties are either present or lacking in XBAP and Silverlight applications. I've heard that XBAPs are intrinsically limited in certain ways due to security concerns, but that's about it. I know for a fact that WPF is robust enough to be used in full-scale business