Here are two similar articles:
1) https://learn.microsoft.com/en-us/windows/uwp/design/shell/tiles-and-notifications/send-local-toast
2) https://learn.microsoft.com/en-us/windows/uwp/design/shell/tiles-and-notifications/send-local-toast-desktop
I can't get info one thing. First article provides tutorial for notifications for apps. Another article shows tutorial for Desktop C# app. What to choose and what are the differences? Thanks.
When they call them apps like what they mean that are the apps made with the new technology called UWP (Universal Windows Platform) which only work with Windows 10. You can see it here.
Prerequisites
To fully understand this topic, the following will be helpful...
A working knowledge of toast notification terms and concepts. For more information, see Toast and action center overview.
A familiarity with Windows 10 toast notification content. For more information, see toast content documentation.
A Windows 10 UWP app project
Then what they call Desktop C# app, are the "classic" ways to do windows applications. For example WPF (Windows Presentation Foundation) in C# which runs in most Windows machines, like Windows 7 or Vista, also they meant the application made in c++.
The main difference is that what they call apps are the ones made with UWP, these ones work well on windows tables, windows phones, and so on.
And desktop c# app
is an app created with WPF which is a little older but works in older OS's.
Related
I have seen this excellent post SO.
As most do, I began a new simple project that has no UI requirement. I noticed the Blank App ( Universal Windows ) option. What is the difference between that and a Console app?
I need an executable that will do some coverting of tiff to pdf type work on a every so often basis. ( every 30 minutes )
I also do not want a service, as in this case there is no need for it to constantly run
Universal Windows Blank app refers to Universal Windows Platform (UWP).
It uses a subset of .Net Framework, also has some parts that aren't in .Net Framework (thanks to #DavidJ comment) and has some other app behaviour limitations. It's used for apps running on wide range of devices like Windows PC, Windows phones, Xbox and other Microsoft products.
Look at particular quote:
Windows 10 makes it easier to develop apps for the UWP with just one API set, one app package, and one store to reach all Windows 10 devices – PC, tablet, phone, Xbox, HoloLens, Surface Hub and more.
So there's no need to use it just for Windows_PC_only console application.
More links:
https://en.wikipedia.org/wiki/Universal_Windows_Platform
https://msdn.microsoft.com/en-us/windows/uwp/get-started/whats-a-uwp
I am new to wpf. Hence, kindly co-operate with my questions.
I want to build an app that runs on windows tablets. This is not to windows store app, rather, I will be developing this app for some company to visualize the data they have. And they will use this app on tablets or other touch enabled devices.
Background:
App will have some graphs and other visualizing diagrams. And WPF MVVM pattern will be used to develop the app.
My question:
My current system is:
System: HP elite book revolve 810 g2 tablet
.NET Framework: 4.0
Visual studio 2012
Can I develop a tablet app with the above specification?
where can i find coding documents on coding for touch devices in WPF mvvm pattern?
How can I use graph or any other visualization method in wpf. I mean, do I have any library that provides API's for different graphs?
Please help me in answering above.
Thank you
This questions will lead to long answers.. I´ll try to make it short!
The elite book revolve has an I5 and Windows 8 / 8.1. You should not have problems developing Widnows apps with that.
Visual Studio 2012 is fine as well, you might want to download the windows phone toolkit (if you want multiplatform apps).
You will need to use framwork 4.5 to develop Windows 8.1 RT apps though - and this is what you want to do if you want multi device apps. If not then it`s just normal Windows applications that can olny be runn on Windows devices (not Windows phone, or RT tablets)
It seems you are a starter in developing Touch apps.
2.1 Honestly you should consider buying a book before developing. The "Windows 8.1 Apps with XAML and C# Unleashed" one is really good
one - you can even read a good share of the first chapter with example code (see links below)!
2.2 I added a few links to ressources that could help you. Consider looking at MVVM, WPF and Touch coding independently. There are tons of tutorials available!
2.3. Doing touch support is pretty straightforward, it`s just another event handler (touchdown instead of mouseleftbutton down) so all you need is to know how to best handle events in MVVM (link attached below). Another thing is gesture support (see link)
Here is the standard library of xaml controls.. pretty basic but you can do a lot with them: https://msdn.microsoft.com/en-us/library/windows/apps/xaml/hh465351.aspx
if you need better /more graphical controls you might consider using Developer Express or similar APIs
heres a list of the graphic tools they provide. Pretty neat: https://www.devexpress.com/products/net/controls/winrt/
Theres also a WinRT XAML Toolkit available: https://winrtxamltoolkit.codeplex.com/ (Tutorial and Graph Preview see below)
Additional Links:
Windows 8.1 Apps with XAML and C# Unleashed (example with code):
http://ptgmedia.pearsoncmg.com/images/9780672337086/samplepages/0672337088.pdf
MVVM General developing: https://joshsmithonwpf.wordpress.com/a-guided-tour-of-wpf/
MVVM in Windows 8: https://msdn.microsoft.com/en-us/magazine/jj651572.aspx?utm_source=rss&utm_medium=rss&utm_campaign=mvvm-using-the-mvvm-pattern-in-windows-8
WinRT XAML Toolkit Tutorial (Windows Store example):
http://eren.ws/2013/10/15/using-graphs-and-charts-in-windows-store-apps-boredom-challenge-day-11/
Best way of event Handling in MVVM (needed for Touch event handling):
What's the best way to pass event to ViewModel?
We have existing Windows Store application which is developed using C# and XAML. We want to port the same to Windows 8 Mobile application. Is there any Guidelines available for this ?
Well at first I would start figuring out the differences
http://msdn.microsoft.com/en-us/library/windowsphone/develop/jj681690%28v=vs.105%29.aspx
http://blog.markedup.com/2013/07/winrt-windows-phone-8-code-sharing-pitfalls/
When I ported two of my (smaller) apps, I put as much in a PCL (portable class library) as I could. All the stuff that remained in the project itself needed to be rewritten. If you have well-maintainable code, there should be only UI (what you have to adapt anyway) and very few platform specific code (like accessing filesystem, camera or whatever) left. This is the part you must redevelop.
Dnt know how you have made these applications well If you have followed MVVM pattern then it is very easy to port windows and windows phone apps from one to other. You just need to take care of new XAML UIs every thing except some platform specific liberalizes will work. While making any of windows store and windows phone application you should use the liberaries that both platforms can consume. For example you can use LEX.db for the database.
here are very good explanations for it.
sharing code between windows phone and windows 8 app -1
sharing code between windows phone and windows 8 app -2
hope this will help
The answers given so far are quite good. One thing to note is that Windows Phone 8.1 is about to be released, which will share many of the WinRT libraries. This will mean that in a few months (as early as May), the shared libraries between the two platforms will greatly increase. You can download the leaked SDK to see what some of the changes will be.
Not that you should wait until then, and creating a PCL is definitely going to help you (especially if you want to later move to iOS, Android as well). It's just something to keep in mind.
I need to set the Windows 8 Application Launcher to launch my WPF application as guided here: http://msdn.microsoft.com/en-us/library/dn195617(v=winembedded.81).aspx
Is it possible or does it have to be a Windows 8 App (instead of a regular WPF application)?
If its not possible, how difficult would it be to migrate my WPF application to a Windows 8 App format?
Couldn't i simply package my WPF application with an AUMID?
Important: The Windows 8 Application Launcher also has a KeepAlive option in Windows Embedded. I need it to keep my application alive as well incase its closing so a good solution would include this as well. Of and i'm using ClickOnce for auto-update my WPF application and i would like to keep this functionality too.
your example is for win 8 Embedded and only for apps. There you have the possibility to startup directly an app.
I think there is still startup possibility for your wpf application on normal Windows 8 devices.
Maybe you have to disable metro on startup. Here is a complex tutorial about this. In Win 8.1 there will be a simple option inside the properties of the taskbar.
Judging by the page you linked, it seems you are out of luck. Only Windows 8 apps are mentioned. But maybe there is another mechanims to auto start desktop applications?
The difficulty of migrating a classic WPF desktop application to a Windows 8 ("Store") app depends on the kind and content of the application, ranging from simple to impossible.
Windows 8 apps are sandboxed and cannot do everything a desktop application can, they have a different lifecycle and different UI/UX principles (you probably need to redo your UI from scratch). .NET and XAML for Windows Store Apps look like .NET and WPF for desktop applications, but there are many surprising details and strings attached, possibly complicating a direct port.
Application Launcher is for Windows Store Applications only. However you can achieve the same effect with Shell Launcher for any executable.
Have a look at these two links here:
http://msdn.microsoft.com/en-us/library/dn195623(v=winembedded.81).aspx
http://technet.microsoft.com/en-us/library/dn451259.aspx
Let me know if you need additional help.
I would like to have some basic communication between some apps we are building. I have been researching on wifi direct, which sounds perfect, but I cannot find much information on it for Windows 7 and WPF (C#).
When I search around all I seem to get is Windows 8 support and Android questions.
Is this a standard that has been implemented by Windows 7? Can I use the features in a C# WPF app? If so, some reference materials would be great if you know of any.
Thanks.
Wifi direct is not implemented in Windows 7, although there may be some 3rd party apps available that implement it.
It is a new feature built into windows 8. Here's a presentation that goes over the feature in detail: http://channel9.msdn.com/Events/Build/BUILD2011/HW-329T