I want to write an application in .Net that has to be shipped with USB drive by the manufacturer. Rightnow application targetted to run only in windows. But will have to support other opeating system in future. Is that app needs to be shipped as portable application? What is required in order to run a .net app as portable app in USB drive? If .Net is not a good option, what are other platform that helps to implement this?
Do deploy .net applications without .net you have to use tools like Xenocode: http://www.xenocode.com
To run it on others platforms, have a look at the Mono Project: http://www.mono-project.com
Related
u-blox's u-center is a desktop application for Windows OS that is light-weight and accommodates all the streamed data without problems.
What is the toolkit or framework (.Net "I doubt it", Win32 API, MFC) used to build such a desktop application like u-blox's u-center?
It is based on Win32 API and MFC. MFC is statically linked. See also the second page of the user manual.
https://www.u-blox.com/sites/default/files/u-Center_UserGuide_%28UBX-13005250%29.pdf
I want to create an IoT application in VisualStudio 2015 community and want to add a reference to Windows Portable Device, which is a COM library. But the whole COM tab is missing from the references window. Is there a way to include COM libraries in Windows 10 Core IoT, or is that impossible? If the second, does that mean I would have to write drivers for any USB devices myself?
Windows Core libraries are included. Many legacy libraries have been reworked into those core libraries. I suggest checking the core libraries for the functionality you are looking for. Libraries need to be compatible with the Windows Universal Platform.
You will need to write drivers for non-supported devices.
I have a confusion regarding Windows Store/Windows 8 app development. When creating a Windows Store app in Visual Studio 2012 and publishing it using Windows Store, what are the devices this app will be available at?
Will a single app be available on all mobile, tablets, and desktops? Or versions will be required to created separately like in iPhone/iPad scenario?
For most apps, the app will be available on any device running Windows 8. The actual hardware form factor does not matter.
Now, if you leverage APIs that are unique to a particular CPU architecture (ARM vs. x86/x64, for example) then you will need to target each architecture separately. A typical example would be if you are using SQLLite in your application. The SQLLite binary is different on each platform, so you would need to do separate builds of the application, each targeting the appropriate architecture. Thus, it is possible to build an app that only runs on x86/x64 and not ARM, for example. Again, the form factor does not matter.
UPDATE: Missed it the first time, but WP8 is a separate platform. You can share code using things like Portable Class Libraries between Win8 and WP8, but they are separate Stores, separate projects, separate builds.
I have a 64-bit-only application that I am developing in Objective-C on Cocoa. It includes various plugins that are also 64-bit. One of these plugins needs to use a 3rd party Framework that is only built for 32-bit i386. It is a C-based framework. It is not possible for the 3rd party to produce a 64-bit version at this time.
I do not want to change my entire application and plugin suite to be 32-bit just to accommodate this one 32-bit framework, but I also do not have any alternatives since it provides access to a proprietary piece of hardware and is the only means my application (via the plugin) will have to operate the device.
What are my options for making this all work?
Clearly my plugin needs to be 64-bit, otherwise the main application will not load it. However, In that case I cannot link against the 32-bit external Framework. I have read that I may need a 32-bit helper application that the plugins communicates with, but have no idea if that is a good or recommended approach.
Are there any other ways to do this? If not, can someone point me to any documentation or tutorials on making this work?
An option would be to create a standalone 32-bit application that uses the framework and controls the device. Then have a 64-bit plugin to your app that launches the standalone app and communicates with it through some IPC mechanism.
Is it possible to make an vb.net application portable?
It is portable - build your .exe and copy it on your flash drive. Assuming it will be run where there is .net framework, there is no problem!
EDIT: A similar topic here: Writing USB Drive Portable Applications in C#
"portable" has more than one meaning, but if you mean a program that could also run on linux or mac than you need to think mono. Specifically, look at their migration analyzer.
Depends on what you mean by "portable". Certainly, you can build them without external dependencies on things like config files, registry settings, etc. You'll still need the .NET runtime installed on the target computer, though.
I seem to recall that you can use vb.net to write Silverlight apps; once compiled, this should be fairly portable (onto all Silverlight / Moonlight enabled browsers).
Of course, if you talk about web apps, the client (html) should already be portable, regardless of the server.
Whether it's a desktop application or a web application, the .Net framework needs to be installed on the machine that the app is run on. Generally, the .Net framework is installed with Windows.
It has to be the same version of the .Net framework as the app was developed in (1.0, 1.1, 2.0, 3.0, 3.5). Which version of the framework is installed depends on the version of Windows.
Just a thought!
Maybe you can make your app executable the normal way (with setup) and then make it into a portable application online using service described at
http://www.abtevrythng.com/2011/12/make-portable-applications-online-for.html#ixzz1flSBi6dZ
You can try to use the online portable app "converter" Cameyo to do it. Just install the Cameyo app, launch it, then install the application you made.
You must use VS 2015. Make all your reference dll's to be local copied. Build your solution (with no deploy file extension (publish-> options->deployment))and merge the exe file with your dll with ilmerge ( http://www.microsoft.com/en-us/download/details.aspx?id=17630 ) (download ILmerge-GUI too) from the Microsoft web site. And have good luck