Create Windows CE application installer, VS2008 - vb.net

Just wrote an application for Windows CE 6, how do I package it into an installer so I can distribute to customer?
I am using VS2008 (VB.net), .NET 3.5 CF

You can create a new Smart Device CAB Project in VS2008.
Just follow the Walkthrough: Packaging a Smart Device Solution for Deployment on MSDN.

Also there are some tools which allows you to Create CABinet packages that can be used to install applications on Windows CE / Mobile platforms.

Related

Application development Windows Embedded Compact 7.0 for Motorola MC32NO

I am trying to get started on application development for my Motorola MC32N0 device running Windows Embedded Compact 7.0.
This tutorial explains that I need a Board Support Package (BSP), however I am unable to find this on the Zebra website. Is a BSP available for the Motorola MC32N0, and where can I find it?
Another question, during the installation of Platform Builder 7.0 I used a trial license key. Now if I deploy the build output to my device, will it replace the OS that is already installed, or will it just deploy the application?
I am new to Windows CE, but have a background in web development and WinForms.
For C/C++ application development, Visual Studio 2008 and the Motorola SDK will suffice.
BSP's on the other hand are for developers working on low-level code such as the kernel OAL and device drivers. Platform Builder 7.0 is a plug-in to Visual Studio 2008 that enables building and debugging BSP code, and is not required for application development either.
If you only intend to develop C# applications, you may not even need the Motorola SDK, but could target just a generic Windows CE device in Visual Studio.

wix burn installer requirements

I was looking for some documentation which will explain what requirements of my installer will be if I made it with wix and burn...
I`m still not sure about that because that information is hard to get...
When I was looking for an answer i found dependency of VC++redist... so it is telling me if I wrote custom action in c++ I need to have these on my target machine?
Also If I want to have my own UI, using burn... automatically I need .net framework 3.5?
I want to write installer, with custom actions and custom UI, I don`t mind which language use to write custom action (c++ or c#) but I want to be able to use my installation on winxp...
So if anybody have some info about requirements of installers... I did just couple of simple installers... all of them are running on win7 all right... but what about winxp? Thanks
Note that WiX is not an installation environment of its own. To put it simply, it is a comfortable, XML-style way to describe your installation requirements that gets translated into Windows Installer .msi databases by its compiler and linker. In this respect, WiX is a relatively thin wrapper around Windows Installer technology, and while it does provide extra features to help the setup developers, its abilities are dictated by the underlying technology and its limitations are not of its own but the limitations of Windows Installer itself.
System Requirements from Windows Installer 3.1 shows this:
Supported Operating System
Windows 2000 Service Pack 3, Windows 2000 Service Pack 4, Windows Server 2003, Windows XP, Windows XP Service Pack 1, Windows XP Service Pack 2
Windows Installer 3.1 Redistributable supports Windows 2000 with Service Pack 3 or later, Windows XP, Windows XP Service Pack 1, Windows XP Service Pack 2 and Windows Server 2003. Windows Server 2003 Service Pack 1 contains Windows Installer 3.1 and therefore can't be installed or upgraded by this redistributable.
So it should work like a charm on xp machines.
Sources:
WIX Tutorial
MSDN

developer platform for Windows RT

Can you make me clear which delevoper platform I can use for delevop Apps for Windows RT (not full Windows 8!). Are some projects templates in Visual Studio which are allowed me to use only WinRt without .NEt during my development on c# and xaml.
The Visual C#/VB/C++/JS|Windows Store app templates (Blank App, Grid App, Split App) are for apps that will run on Windows RT and any other Windows 8. You can use .NET on Windows RT, but if you don't want to - you can also use C++ or JavaScript. Note that Windows RT is the SKU of Windows that runs on ARM tablets, while WinRT or Windows Runtime is the new generation development platform for Windows. Also note, that while most parts of Windows Runtime can be used only by Windows Store apps, some can be used by both Windows Store and Desktop apps, some can only be used by desktop apps and I think some parts of the old WinAPI/Win32 might be accessible to Windows Store apps too. MSDN documentation states which APIs apply to which types of applications.
You can use Visual Studio 2012 Express for Windows 8.0.
More info on msdn.
The project templates are available under Windows Store category under Visual C# in New Project in Visual Studio.

Building Sharepoint project on 32bit machine

My buildserver is a 32bit system.
I heard that to run and develop sharepoint projects I need a 64bit machine.
Is it feasible to build a sharepoint project on a 32bit system?
Answering my own question:
It IS possible to build Sharepoint projects on a 32bit 4.0 Framework with msbuild. Also those can be deployed to a server.
As far as I know, no. You'll need an x64 box to build it on. Note that with team city you get 3 free build agent licenses so you can always toss the build on another machine.

Deploy the application. NET for Windows Mobile 6.x

created in a prjeto. NET Compact Framework 3.5 for Windows Mobile 6.x.
I wonder how you do to create the installer (. cab) for this project?
How do deploy. NET Framework and SQL CE for Mobile?
Given a novice user.
Today I have an installer.cab and .msi for Windows
But to my system running is to install the SQL CE and Compact Framework 3.5. How to download and install these applications after the installation of my system?
Would not want to send these applications together because the size of the installer can get big
Thanks.
You're going to want to do a multi-CAB install. MSDN covers it here. CodeProject here.