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.
Related
VS 2012 published web service and click once deployment of a Windows forms application based on VB.NET and .Net 4.0 don't serve up the newer version of the software. They keep on serving the previous version. However it works fine with VS 2010. This is on IIS 7/7.5.
Anyone have any idea about it?
Thanks.
Never mind. I had to clean and rebuild. VS 2012 added an extra step over 2010.
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.
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
Background
We're using System Center 2012 to deploy a Windows 8 Metro-style application to Samsung slates in the field running Windows 8 Enterprise x64. The slates are joined to the domain and have a persistent DirectAccess connection back to it, allowing System Center to push applications and updates to the devices.
We have to deploy our application to potentially hundreds of devices in the field, which is why we went the System Center route. The code signing cert is installed on every device using Group Policy. To deploy the application, you simply provide the package output and specify the collection of devices to install it on. The app just shows up on the device in a few minutes.
The problem we're having is that when System Center deploys our application, the SQLite dependency is lost and none of our data access works.
About our project
Our application is a WinJS application that uses SQLite as a backend. However, all our data access code is in a C# WinMD project which the WinJS project references. We're using the sqlite-net library to talk to SQLite - we included the source for that in our C# project.
In Visual Studio, we installed the SQLite for Windows Runtime extension as described in Tim Heuer's article. The Metro application references this.
Testing using other deployment methods
SQLite data access from the application works fine when you debug or run it locally - in both Debug/Release and x86/x64.
The app packaging process provides a PowerShell script that you can use to install the application and a developer license if necessary. When installing our app using the PowerShell script, SQLite data access also works fine. Verified this by packaging and installing both Debug/Release and x86/x64 versions of the app.
Troubleshooting
When the application first tries to use SQLite, we see an exception about it not being able to find the sqlite3.dll.
We've tried/verified the following:
Confirm that we're deploying a Release/x64 build
Examine the appx in WinRAR and verify that it contains the sqlite3.dll
Reference the "SQLite for Windows Runtime" extension from the C# project instead of the WinJS project
Also reference the C++ runtime, this caused System Center to fail when deploying the app. Don't know why yet, but looking into it.
UPDATE
The issue is that System Center is having trouble deploying the Visual C++ Runtime Library dependency that the SQLite library needs. So unfortunately this isn't a programming question anymore. We're getting some help on this and I'll post the fix.
I wanted to post the details of a temporary fix that we're going with. We've also gotten closer to the root of the problem, so I wanted to provide those details as well.
Recap of Issue
When referencing the Visual C++ Runtime Package from our Metro project, System Center is unable to deploy the application to the devices because there is a problem deploying the proper version of the dependency for the appropriate architecture and build flavor.
Our development machines running Visual Studio 2012 (and packaging the project for deployment) are using a newer version of the Visual C++ Runtime (50727) than what is available in a fresh installation of Windows 8 (50712).
Worked with the System Center team and confirmed that this was a bug in the version we were using and has already been addressed in future builds. We're going to work on upgrading the environment but that will take a couple of weeks.
Workaround
I confirmed and tested the following workaround:
Remove the reference to the Microsoft Visual C++ Runtime Package from the Metro project
Install the x64 version of the Visual C++ Redistributable for Visual Studio 2012 - http://www.microsoft.com/en-us/download/details.aspx?id=3
Deploy the application
Works like a charm because the correct version of the dependency is there already. Obviously not a long term solution if we choose to also target x86 and ARM, but will get us over this hump.
I found that links:
Microsoft .NET Framework 4 (Web Installer)
Microsoft .NET Framework 4 (Standalone Installer)
Microsoft .NET Framework 4 Client Profile (Standalone Installer)
Note that (2) the size is 48.0 MB and the (3) the size is 41.0 MB. It's not the REAL .Net 4 Full Standalone. :(
I want that installer in a usb pen drive because my app need of features of .Net 4 Full Framework (like MSBuild) and I will install in a enviroment without Internet access.
PS: I tested the (2) and really is the Client Profile with another name... :(
Actually, you already found the full .NET 4 SDK. Microsoft put in a lot of effort to decrease the size.
The Microsoft .NET Framework 4
redistributable package installs the
.NET Framework runtime and associated
files that are required to run and
develop applications to target the
.NET Framework 4.
Have a look at this hanselpost.
The prerequisites have changed since .NET 3.5 SP1, .NET 4.0 requires at least XP SP3, Windows 2003 SP2 or Vista SP1. .NET 3.5 could be installed on any version of these operating systems, including a 11 year old completely unpatched version of XP.
So the 3.5 installer also needs to be able to update a bunch of native Windows components.
Not having to include the Windows component updates and additions allowed for a significant size reduction. If that's an issue then you'll have to include the Windows service pack installers on your pen drive.