Can i place my libraries in some where over the internet and load them from cloud each time the app runs instead of being placed beside the *.exe file ?
As far as I know, Prism does not provide the functionality to do this in desktop applications as out of the box. However, Prism allows you to extend its functionality by implementing your own versions for some of its components. For this particular case I believe you might need to create your own implementation of an IModuleTypeLoader that obtains the files from the cloud instead of the local file system. You can check the FileModuleTypeLoader implementation of Prism and use it as a starting point.
Related
I have a bit of a predicament in which I am seeking some advice and I currently have limited knowledge with regards to whole Universal applications.
I currently have a Winforms application that needs to call the CameraCaptureUI control; however, it turns out that this control is native to Windows 8.1 and Universal applications.
At first I was going to convert the application to a Universal; however, this isn't a possibility since it relies on some third party software that isn't available as portable library targetting the .Net Core fraemwork, and is unable to be converted to one at the time.
I thought I might go with a portable library, but this was a deal breaker b/c I couldn't reference the CameraCaptureUI control.
My next logical step was that since this class is unavailable via a regular Winforms project, I thought I could add a Universal project to the solution and use it as a wrapper to call the CameraCaptureUI. I could then perform the processing I needed from within the other executable by seting up a ProcessStartInfo pointing to the executable of the Universal application and wait for it to complete. This would be fine; however, you cannot run a Universal application without the context of an app container.
That brings me to my current predicament. What would you recommend as the best approach to tackling this? I really need to call the executable from the Universal app, or at the very least the CameraCaptureUI, from within the Winforms application. Calling the Camera straight up isn't an option because I need to be able to retrieve the photo(s)/video(s) the user took. I'd also like to keep it to a single installation instance. We do currently use ClickOnce as our deployment method.
Has anyone else ran across this before or could offer some suggestions?
Any advice is greatly appreciated!
Thanks,
Nathan
I have a windows phone class library that is built for windows phone 7.0(coded in c#). Is it possible to port the same class library to windows 10 mobile sdk?. Or, do I need to write the entire class library from scratch to support windows 10 mobile.
It is possible to port it, but not in an automated way.
UI components should be relatively easy, as long as not a lot of
third party controls such as Telerik for Windows Phone were used.
Third party libraries need to have been ported to the WinRT platform
(or UWP, as it it called now) as well, which is not always the case.
Most of the XAML can be re-used, but some namespaces, events and properties are named differently (eg: Tap becomes Tapped).
Some layouts may need to be reworked a bit due to a different approach in scaling (Silverlight scaled everything up, as it pretended a screen is always 480px wide).
HTTP calls: This is probably going to have to change a lot, depending
on how they were implemented in your WP7 library. Webclient no longer
exits in WinRT, HttpClient or creating your own HttpWebRequest is the
way to go. Since WP7 apps did not have async/await by default, I
would suggest rewriting this part.
XML parsing: This should be compatible (maybe some small syntax changes)
I/O operations: Probably massive changes. WP7 used the Isolated Storage mechanism, which has been replaced. Capturing images with the CameraCaptureTask, and basically all use of sensors will have to be rewritten.
Local Database is not longer supported. Use Sqlite if you want to use a database in your app.
The application lifecycle is also completely different in WinRT. Pages in the backstack are not cached automatically and a lot of events in a page work differently, or might not occur at the same time as they were in Silverlight applications
for more info: Move from Windows Phone Silverlight to UWP
Most of UI elements has changed from wp7.0 to Windows10. It will have to completely rewrite. The same applies to WP 7.0 API.
If you has portable library then the problems should be much less
I’m looking for solution on architecting modular application model in WPF. For now I was using Devexpress POCO MVVM for architecting my WPF apps but is lack of modular extensibility and I’m looking something to work well with my current design and allow to build application composed with modules. My expectations are:
Modules are placed in remote location
Framework can download latest version when application starts (or demand module)
Application should load only subset of all modules basing on permissions of currently logged user
Framework allow integration with GUI – allowing to load list of modules and put graphical representation of module in some part of my application
Library is live and not closed project
I’m thinking about PRISM but this framework always looked little complex and heavy but maybe it was wrong impression. Another library is MEF but I don’t know if it fits my expectations.
Can I ask of some suggestion for modern library which will be good for my needs?
PRISM is a large library but is made of many optional parts making it easy to adopt just the parts you need (its not all or nothing).
Specifically it does do modularisation, with on demand load, and it does do UI composition from modules.
Its also open source.
Versions are valuable for desktop apps (WPF), Universal apps (Desktop app, tablet, phone and possibly iOS and Android via Xamarin - but I'm not sure about that!) so there should be a PRISM for your chosen platforms!
I understand my "this" query may sound very generic but any pointers to guide is highly appreciated.
We are building an WPF application based on MVVM design pattern (with DevXpress controls) and want to achieve the following.
There will be one .EXE file which will run the applications.
All my XAML files need to be as DLL [Why? - Reasons specified below].
Call the DLL dynamically and load with in the WPF application.
[Why?? - Reasons]
Our application is a client/server intranet application. We are planning to use ClickOnce deployment to deploy the application. In case there are any changes to the application, my though is we don't have to change the entire application and recompile it and then deploy so the client machines will be updated.
Instead we can change only those screen or XAML file which are needed and update on the server and ClickOnce will automatically handles the updates on the clients. This also, helps us in maintaining our application and less troublesome for the developers and UI designers.
I am welcome to another better approach also.
How can I use it on WinRT (Windows 8) - I can't compile it. Can I use it also with "normal" Windows (WPF)?
There isn't currently an mvvmcross port specifically for wpf - a couple of people have suggested building one, but the majority of users have so far requested more work on mobile platforms instead. There is a current console (win32) port and extending that towards WPF should be quite straight-forward.
Future development is now based around the Portable Library branch - see some info on http://slodge.blogspot.co.uk/2012/09/mvvmcross-vnext-portable-class.html and the code on https://github.com/slodge/MvvmCross/tree/vnext
For WinRT, the TwitterSearch example within the vNext branch is a good place to start - it should compile and work across all of MonoTouch, MonoDroid, WP7, WinRT and Console:
If you find you can't compile then please log specific compiler error messages either here or to github issues.
MvvmCrossLibs\MvvmCrossLibs.sln consists of many projects, requiring different runtimes to be installed to open properly (Mono Touch, Mono Droid, WP7). If you only need the library in WinRT, your best bet is to open Cirrious\Cirrious.MvvmCross\Cirrious.MvvmCross.WinRT.csproj directly and add the missing Newtonsoft.JSON package with NuGet (you'll need to save the automatically created .sln file before that). It should compile just fine after that, at keast it did for me. Now just reference the assembly in your Windows Store app project and start using it.
I don't have any previous experience with MVVMCross, but it doesn't look like it currently supports despktop WPF apps. I don't know how difficult it would be to create/compile such a version, though.