I found something on this documentation page that doesn't make sense to me.
Under requirements, there is:
Minimum supported client: Windows XP **[desktop apps only]**
Minimum supported server: Windows Server 2003 **[desktop apps only]**
Now I understand the difference between an app with a GUI and one that runs as a service, but in the end, they are both processes. I've never heard of this kind of restriction on a function call like this. Is this just poor documentation, or is there something more to this?
With the introduction of Windows 8, Metro, and Windows Store, API documentations now specify which framework(s) they are supported on. Not all desktop APIs are available to metro/mobile apps, and vice versa.
Related
while understanding the differences between 10.0.19041.0 and 10.0.22000.0 SDK ,I encountered
https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/ this page. After looking into it , I understood 10.0.22000.0 is mainly for windows 11 applications .
If we select 10.0.019041 as the package and build the application, won't it run on windows 11.
If we want our application to be run on windows 11 do we need to choose 10.0.22000.0 over 10.0.19041.0.
Please correct me if my understanding is wrong.
Thanks for the help!
TLDR: No, your understanding is wrong. You can likely use whatever version you want and your application will run on both, Windows 10 and Windows 11.
Long with details:
It's true, the 10.0.19041 SDK is for Windows 10.
It's also true, 10.0.22000 SDK is for Windows 11.
Let's have a look from a user perspective:
When you download software, how often do you need to select the correct operating system? Not very often. So, somehow, the SDK version does not seem to be very important.
Let's have a look from a Microsoft perspective:
Does Microsoft want all developers require a rebuild of their Windows 10 programs once they release Windows 11? Certainly not, because this would mean that with the release of Windows 11, there wouldn't be a single application which runs on Windows 11. Microsoft couldn't even perform inhouse tests for multi-million-user software such as Adobe Reader.
Let's have a look from a technical perspective:
The Windows SDK provides the API definitions of Windows. The Windows API is very old. And since Microsoft does not want developers to rebuild and, even worse, let them fix breaking changes, Microsoft keeps that API incredibly stable. They will not change the API, they will only add new API methods.
The chance that the Windows API you use already existed in Windows 10 and still exists in Windows 11 is almost 100%. So your application compiled for Windows 10 will still work on Windows 11.
Likewise, if you compile with the Windows 11 API and don't use the most recent fancy API, your application will still work on Windows 10.
Example
Let's say you developed an application that manages Fonts. You have used the interfaces IDWriteFontSet, IDWriteFontSet2 and IDWriteFontSet3. With Windows 11, Microsoft has added IDWriteFontSet4. As long as you don't use that interface and stick to the previous 3 interfaces, your application will run fine. Once you start using IDWriteFontSet4, your application may crash on Windows 10 (potentially only if the user invokes the functionality, not so sure).
I want to be able to scan a document with my universal windows app.The problem is that The Windows.Devices.Scanners APIs are part of the desktop device family.
Is there any way to check if the app is running on a desktop, and use these API's in that case?
Any other solutions or ideas would be welcome
My Windows App reject by the Following reason:
Depending on the underlying cause of the issue encountered, the following resources may provide useful guidance to resolve:
• "Product ID": Avoid hard-coded logic based on the original Product ID. If your application design requires using logic based on a Product
ID, use the Windows Phone Store assigned non-volatile Product ID instead
Data for Windows Phone | Installation folder": Don’t write to the InstalledLocation folder in your production application release
submitted for certification (http://msdn.microsoft.com/en-us/library/windowsphone/develop/ff402541(v=vs.105).aspx)
Capability Detection": Double check that the capabilities required by your application are declared correctly. You can do this by running
the Windows Phone Capability Detection Tool, as described at How to: Use the Windows Phone Capability Detection Tool
(http://msdn.microsoft.com/en-us/library/gg180730.aspx).
Note: But My app working in my windows phone(Nokia Lumia 510) and Emulator.
I have totally confused what mistake i done in My Application.
Please give a suggestion. I am wating for all reply
Try testing on Windows Phone 8. There's been a few API changes in Windows Phone 8, which may result in failure on some functions, which works well in Windows Phone 7.
Most likely the issue is #3 - you're using a capability (data, location, etc) and not declaring it. Your app will still work in the emulator in this case, but will fail certification. Use the tool they mentioned to test this - http://msdn.microsoft.com/en-us/library/gg180730.aspx
We are in process of preparing a testing checklist to make sure that our newly developed windows app (.NET 3.5, WPF) is going to be worked well on windows 7 in all environments.
Since our app is accessing WMI,USB devices(we have a USB blocker),windows power plans since we have power saving utility.
Because of that, we prepared a small checklist to make sure that our app will works well even if users change some windows settings.
Here is what we currently have:
Testing with 64 and 32bit OS.
Testing with OS that is not installed on C:\ drive.
Trying with windows running with/without domain.
Turning off windows installer service and making sure that our app is going to turn it on during installation.
Checking WMI service before accessing WMI.
Testing on laptop/Desktop machines.
We still need more test cases to cover more scenarios.
So if you have any more suggestions, that would help a lot.
Thank you!
How would I develop apps if I had a Cloud Only PC?
I'm looking at the Acer-AC700-1099-Chromebook-Wi-Fi on Amazon.
The idea is kind of neat, and I can see this being the way more PCs are going to go. Nothing installed on your PC - you are basically running a "dumb terminal" that lives off an Internet connection.
So far, the biggest concern has been that apps like PhotoShop can not be run on them.
As programmers, most of us don't care about PhotoShop, but we need to compile our C#!
Does anyone have any information on whether some form of Cloud Compiling is in the works?
Maybe my employer would be able to purchase an X-License copy of Visual Studio that is installed on the server and I'd just log into that to develop all of my apps.
This is totally doable. I would suggest that you/your employer take a look at XenDesktop. This is technology that lets you run Windows Virtual Machines in your own private cloud. Then to access these machines you run a "thin client" which is basically like a Remote Desktop session. The thin client can run on a normal laptop, an iPad, and even Google ChromeOS. The basics of this technology are free, and not that hard to setup.
See these articles here which are Citrix announcing support for ChromeOS.
http://www.citrix.com/English/NE/news/news.asp?newsID=2311983
http://lazure2.wordpress.com/2011/05/12/chromebook-box-with-citrix-receiver-going-against-microsoft/
The coolest part about this, is you are using a Chromebook which is a cloud only laptop to access the public cloud AND your own private cloud. Pretty cloudy in here :)
Given that Visual Studio is Windows-only, you have to run Windows somewhere - either on your local PC (not an option with Chrome) or on some remote server (and access it via some web-based RDP client IF such beast exists and works with Chrome). I.e. the question can be split in two - where to get the powerful server system to run VS on it (and don't forget that compilation is resource-consuming, so the server system is to be very powerful if several users work on it in parallel), and how to connect to remote Windows system using Chrome OS. Both of those questions are offtopic here ;).