Could you take a look and give me some suggestions?
-
Hello All, Let's say I have the existing WPF application. There are two kinds of clients who are willing to install my software on their machine and who prefer to use my software like web application without installing on their machine. I don't like to have two seperated applications (WPF Application and Silverlight Application). I just want to have one application so I'm not so sure what I should do. During these days, I'm just surfing around the internet and collecting the information to make good decision. 1) I think it would be fine if I keep WPF application with ClickOnce for those clients who are willing to install my software on their machine. Can I have an XBAP for those are not happy to install my software? Actually, I don't want to have the seperated applications such as WPF and XBAP. I will have only WPF application but when I deploy that project, I will deploy with ClickOnce once and I will deploy it as XBAP once. Is it possible to do? or Is there any way to convert the WPF project to XBAP project in very easy way? or should I have two differnet applications for two different users? 2) I know there are some differences between WPF and XBAP. Here is the list that I found. Could you please correct me if I'm wrong? 2.1) The client need to install .NET 3.0 or above. 2.2) Coperate Proxy may block the exe file for Xbap application. 2.3) XBAP runs on sandbox so that it has the following limitations ---------Windows and Popup won't work. We need to convert it as a Page. ---------can't use BitmapEffects and Image Encoding ---------Only run in IE6/7/8 browsers and Firefox ---------supports only Windows XP SP2 and later, Server 2K3 and later, and all flavors of Vista ---------XBAPs doesn't work in Windows Vista Sidebar, ActiveX does! ---------You cann't connect the database directly. ---------unable to load a custom mouse cursor in an xbap ---------SaveFileDialog ---------Cross Domain Access ---------File System & Registry Access ---------WindowsForms Interop ("Crossbow") ---------XAML Serialization (via XamlWriter.Save) ---------Full Speech Support ---------RTF Clipboard ---------Full XAML Clipboard Support ---------Drag & Drop ---------HwndHost 3) Some articles said that if we are using ClickOnce, the application will be installed to the client machine. but if we are using XBAP then, it won't install to the client machine and it will be cached. Based on my research, I totally don't agreed with this statement. Xbap application will be downloaded into the A