How to develop winforms (like .net winforms) for Mac Os?
What language needs to be used if need to develop app quickly, if there is lot of overhead using .net for Mac?
Please share your quick useful thoughts.
Thanks in advance,
Karthick
Mono, if you are used to develop in C# .Net.
http://en.wikipedia.org/wiki/Mono_(software)
http://www.mono-project.com/Main_Page
Related
We have developed a WPF application runs great on Windows 10. At this point we are looking for ways to run this software on a Minnowboard. This board has a Windows IoT OS. As I've seen it is only capable to run UWP applications. Is there any way to make our app run under IoT? Thanks.
Of course you can port your code. Depending on how complex your app is, it still might need some rewriting as many APIs are not available anymore, have changed or were added.
Maybe these links help you:
Move from WPF and Microsoft Silverlight to WinRT on MSDN
UWP Bridge tool by Mobilize.NET
UWP samples by Microsoft on Github
Windows 10 IoT Enterprise version enables WPF apps
Im developing a Desktop app with WFP, but I've to migrate it to UWP Windows 10. Does anybody knows what this conversion involves? How complex is it?
Thank you in advance for the help :)
XAML for WPF and WINRT is not same because lot of classes which exist for WPF are missing in WINRT library. So the porting may have lots of work to do.
This may be helpful to you: https://channel9.msdn.com/Events/Build/2015/3-741
If you are going to convert it from WPF to UWP be sure to keep an eye out for the next few things:
ASync calls
a framework with less options but same possibilities
depends on your code and programme, but if you are experienced it might only take a few hours :)
.NET in WinRT is a lot more limited than the one in WPF.
So the level of difficulty of porting directly depends to your app's functionality.
I am working on a project where there is requirement of GUI to be created in Silverlight. Some key requirements are:
Extremely rich GUI
Real time visualization process graphics
Support multiple themes
Support different display size
Support charting / trending controls
Same functionality for Desktop / Web using same code base
Same functionality to be available on embedded controller (based on Windows CE)
I understand that using Silverlight we can have same codebase for desktop / web applications. However challenge is to have the Silverlight application (windows and/or web) for Windows CE. I would like to understand what is the best way to implement Silverlight application on Windows CE with as much code reuse as possible.
I would appreciate if you could provide some inputs on what should our architecture approach be for this application development. Also, please let me know if you need more inputs on the requirement side...
"Silverlight" for Windows Embedded (SWE) is a bad name. It's not really what most would call Silverlight. It's simply a XAML-based engine that you can use Blend to develop for. For Windows CE, you must use C++ to develop for SWE. You cannot reuse SWE assemblies in other Silverlight projects. You cannot use other Silverlight assemblies in an SWE project. Your XAML itself will probably have some reusability, but XAML sharing from a code perspective is a challenge in its own right.
I am Really confused by reading some articles about Silverlight. Whether I should concentrate on WPF or Silverlight or Both?.
It's like asking Web or Desktop : Which one has upper hand?
Silverlight (Web) and WPF (Desktop) Both are similar. But both have their separate workplaces.
You cannot have a Windows Calculator, Task Manager or MS Word (please don't mention google docs) applications on web like they are on desktop. And same thing applies for web applications.
So, it depends on what platform you want to work on.
I dont think its difference between Web and Desktop. Silverlight is still pretty limited by platform it can run on and still requires some local runing process, even in the sandbox.
I think difference here is features vs availability. WPF can give you features of whole .NET framework, total acess to users's computer and some features that are not available in SL. SL on the other hand allows you to run your app on some different systems (Windows, Mac and there is limited support for Linux-based systems), distribution is much easier thanks to web deployment and whole application can be part of your web ecosystem.
Iam personaly for WPF, but thanks to this whole web and cloud-hype in the last years, SL is getting much more attention from side of MS and developers in general.
Reading these questions and their answers may give you some insight into this:
Definitive source(s) for the difference between Silverlight and WPF
https://stackoverflow.com/questions/1254937/wpf-vs-silverlight
What is the difference between WPF and Silverlight?
I totally agree with decyclone, it depends on which platform you want to work. If you have prior experience Asp.net/We applications Silverlight is the way whereas if you have worked in WinForms/Windows applications then WPF is the way to go.
But yes most of the concepts in both SL and WPF are similar; so once you have good understanding of those concepts, you work in either without much problem.
If we ignore the platform then WPF is having the upper hand as WPF is kind of superset of SL.
Have a look at this SO question too -
Learn Silverlight or WPF first?
We've developed a WinForms application (targeting .NET 2.0 with VS2008), we've just found out that we need to localize it for use in another language (other than english) :( What are the guidelines for developing multi-lingual languages in .NET?
Another application borrows Paint.NET's idea of globalization (using resources) but I was wondering if there are tools out there than can automate this for us - free would be nice but commercial is OK too.
Any ideas?
How do people normally work on projects that require multi-lingual interfaces? We're talking WiNForms apps. Do you just use IsLocalized = true and let .NET handle it?
You should create assemblies for each language. This article is a good point to start from.
To automate localization process you could use 3rd-party tools, like ResX Localization Studio.