As part of an internship project, I am looking to deploy an application on PC (Windows 10) as well as on mobile digital media such as tablets.
I have some programming knowledge in VB.Net and have the Visual Basic 2010 Express IDE. Is a Windows Forms Application executable on Windows 10 tablets? If yes, are there compatibility issues (e.g. tactile events)? I am looking for the most suitable equipment for daily use for production monitoring operations. All the devices must have access to the same database to draw up daily reports from a master tool (a PC).
Is a Windows Forms Application executable on Windows 10 tablets?
Yes, Windows 10 tablets are able to run traditional Win32/.NET desktop applications. Please refer to the following article for more information about this: https://www.windowscentral.com/windows-10-arm-not-windows-rt.
As mentioned in the comments, you should be aware of the fact that tablet users may excpect a more touch friendly UI compared to what a traditional Windows Forms application may offer by default though.
If you intend to target only Windows 10+, you might want to to take a look at the Universal Windows Platform (UWP).
Related
Recently Microsoft announced ability to create universal applications in Visual Studio 2013. Is there any easy way to convert existing Windows Phone 8 application into universal or i have to create new project and properly move the code manually?
It is not about converting a project type or moving code. You will have to port your app from one runtime to another. This is because the Universal project templates use the Windows Runtime APIs where as your existing Windows Phone 8 application uses the Silverlight APIs.
Windows Phone Store apps use the same app model and UI framework as Windows Store apps do, and they use the Windows versions of common features such as background tasks. You will still be able to reuse a lot of your existing code, but these differences mean that it really is a porting exercise, more than just an update, to move a Windows Phone 8 to the new app model.
(Source)
There are some features that are available in Windows Phone 8 for which there is no Windows Phone Store (Universal apps) equivalent. See more here.
The right-menu option is "Add Windows 8.1...". That will add Windows 8.1 support and add a Shared section to both projects so you can share code between then.
In your solution, right click your Windows Phone application and select "Add Windows 8.1..." and follow the prompts.
I ported my windows phone7 application to windows 8(just copy paste the xaml and c# code in visual studio 2012->new->project->WPFApplication) and made changes in UI sizes.The problem is the .exe file(after building wpf application) runs only in the system with .NET framework installed.I want to run my application in all system running windows(7(32/64),xp,vista).I am newbie to windows application basically wp7 developer.Thank u.
If you really want to port a windos phone 7 app to windows 8, You should go through the following resources. They provide most of the information.
http://msdn.microsoft.com/en-us/library/windows/apps/hh465136.aspx
http://leventoz.wordpress.com/2012/03/07/moving-a-windows-phone-app-to-windows-8-a-case-study-part-1/
http://leventoz.wordpress.com/2012/03/11/moving-a-windows-phone-app-to-windows-8-a-case-study-part-2/
WPF is a part of the .NET framework, so you can't write a WPF application that can run without the framework on the machine.
If you want to create a binary that run on the classic windows runtime you can't use WPF/C#/VB etc.
Best thing if you want to port your Windows Phone app to Windows 8 is to create a Microsoft Store app, File > New Project > Blank App in VS2012. The app won't run on anything except Windows 8 but the Microsoft Store for Windows 8 is probably the best place to have your app if it's ported from Windows Phone.
Migrating application to WP7 is not that easy as it sounds. There is lot of different APIs and also limited async/await in WP7 when using this extension.
I would probably recommend starting with this MSDN article. It describes basic problems and challenges and also contains useful namespace and API mapping:
Migrate/port a Windows Phone 7 app to a Windows Store app
As Microsoft said that windows 8 and windows phone 8 share the same code base. If I use visual studio 2012 RC write an application for windows 8. I want to know whether I can install and run the same application on windows phone 8?
If the answer is yes we can prepare ourselves for windows phone 8 SDK by learning Visual Studio 2012 RC for windows 8 today!
Right now they haven't announced everything, so this is just my speculation.
I guess that you will not be able deploy the same app (xap file) to WP8 and Windows 8. This by design. Why? Because they are very different systems. Your beautiful, fast and awesome Windows Phone app will suck on Windows 8. There is no silver bullet. It's the same for HTML. You have to create separate mobile version of the web app, otherwise nobody will use it.
They share the same kernel and probably plenty of APIs. But that doesn't mean the runtime environment in which your applications run is the same. E.g. very different form factors make it necessary to adapt the app anyway. Since they never said that Windows Phone 8 has the same application programming model as Windows 8 you can at the moment safely expect not to be able to deploy the same app to both Windows 8 and Windows Phone 8.
That being said, you probably can expect to share a lot of code between both systems, especially if you're using either C# or C++ (with native apps coming to WP8 too).
Application compiled for WP8 won't just run on Windows 8, but you can share lot of code into common libraries.
There is a chapter in Windows Phone 8 SDK about targeting both Windows 8 and Windows Phone 8 development. Mostly is possible either by Portable Class Libraries, referencing common files both in W8 and WP8 projects or using Windows Runtime Components.
http://www.microsoft.com/en-us/download/details.aspx?id=35471
Many Application designed for wp8 work on windows8 also as The developer have also to decide whether it will work in both of then,usually windows8 has not enough graphic and motion control so some WP games do not run on windows8,, You can always see any app permission notice to understand whether it work on wp8 or not on other hand there were also some windows game that has as much graphics that WP could not run,,
Like if you want game like assassins creed it will run on both operating system(WP,window) but in different manner
So it's chooses by game properties that define cap package to run or not
My company is planning on developing for Windows Phone 7. The build server we have, however runs Windows Server 2008. According to the Windows Phone SDK release notes I've read that only Windows Server is not supported for the SDK.
Does anyone have any experience on whether there's a possible workaround to have a Windows Server 2008 machine build Windows Phone 7 projects?
Update: I'm interested in building on a WS 2008 as we're talking about a project with a larger team where continous integration and centralized builds are essential. I'd be hoping we wouldn't have to set up an additional Windows 7 build server for this task.
Most the issues of this nature come into play meeting the emulator's requirements rather than the development tools.
With that said some are hacking around the walls put up to stop people going into the unsupported territory of WS2008.
Judging by your requirements I'd say dive in. If you have the option to test on device or in emulators in Win7, that will place you well.
This post likely of interest.
Aaron Stebner's WebLog : How to install the Windows Phone Developer Tools CTP Refresh on Windows Server 2008
If someone is interested here is instruction how to modify ISO image of the WinPhone 7.1 SDK for installing it on Windows Server. Basically it's the same Aaron Stebner solution, the only difference is that you need to modify it in the ISO image.
My company has built a machine that measures wedge and roundness of lenses by reading and interacting with very precise indicators, motors, and a switch panel. The interface for the machine is a WPF application and it runs on Windows Vista on a normal PC bought from the store.
I've never worked with Windows Embedded, but it sounds to me like it's intended for this type of system. My question is, what does it buy me? If I were to run this on Windows Embedded Enterprise (Vista) what benefits do I get?
Do I get more control of the load, login, and all that? Can I make it more seamless where it doesn't really feel just like a normal application running full screen?
Is it something I should look into more?
From Wikipedia, this statement tells the whole story:
Windows Embedded Enterprise brand of Windows Embedded Operating
Systems consist of Windows XP for Embedded Systems and Windows Vista
for Embedded Systems, which are the same versions of the OSes as are
available in retail but are licensed exclusively for use in embedded
devices. They are available for both x86 as well as x86-64 (x64)
processors.
Further confusing this branding decision, the only versions of Windows Vista available under Windows Embedded Enterprise are Business and Ultimate. In non-terse Microspeak, Windows Vista Business for Embedded Systems and Windows Vista Ultimate for Embedded Systems are both Windows Embedded Enterprise products.
Since you're effectively getting the exact same OS, the only benefits to choosing this product over any other version of Windows Vista are your desired licensing. Here's the comparison matrix of Vista products by edition, and as before, you're looking at the columns labeled Business and Ultimate, not Enterprise.
For versions of Windows that have actual tangible benefits in the form of smaller kernels and increased robustness for embedded systems, consider the remaining editions listed on this page.
For the benefit of current users at the time of this writing, this branding decision extends to Windows 7.
Here's the comparison matrix detailing the benefits of Windows 7 Professional SP1 and Ultimate for Embedded Systems. As before, Microsoft's product marketing is somewhat misleading:
These products are fully functional versions of Microsoft’s desktop
operating system intended for use in an embedded solution consisting
of purpose-built hardware and application software.
Here's the comparison of editions. You're looking at the columns labeled Professional and Ultimate again for the features you'll receive with either product offering.
For embedded solutions in Windows 7 that actually involve a customized version of the OS, consider Windows Embedded Standard or Windows Thin PC for slimming down aspects of the OS. Microsoft's documentation is far better than I can tractably fit in an answer here.
Windows Embedded Enterprise is a different SKU but exactly the same OS. You will not get any better control of the load, login, etc.
If you want to do such things, you need to consider Windows Embedded Standard. The actual available version is Windows Embedded Strandard 2009 and is based on Windows XP Pro (which can still run .Net apps) and next release, Windows Embedded Standard 7, will be based on Windows 7. These OS are componentized versions, meaning you start from scratch and agregate the components of the OS you need and just these ones.
More details can be found at: WindowsEmbedded.com