Kategorie-Archiv: mobile Tools

“Ein bisschen Backend”–DNUG Braunschweig am 16.07.2013

Viele Apps, sei es nun Windows, Windows Phone, iOS oder Android benötigen eine Möglichkeit Daten strukturiert serverseitig abzulegen. Ein eigener Server kann hier schon helfen, doch rechnet sich dieser kaum zu Beginn einer App oder einer Idee.
Daher zeige ich in einem Streifzug die Windows Azure Live Services und Buddy.com. Dabei geht es nicht nur um die deine Datenablage, sondern auch um die Mehrwerte, die solche Dienste bieten.

Wann: 16.07.2013 ab 19 Uhr

Wo: Restaurant Zucker (Frankfurter Straße 2, 38122 Braunschweig)

Weitere Infos gibt es hier.

WPD January Update Direct Links – German

Wie sicherlich bereits bekannt, sind die deutschen Dateien aufgrund eines Fehlers nicht erreichbar.

Aus diese Grund hier kurz die Direktlinks zu diesen Dateien:

- VS Jan-2011 Update: http://download.microsoft.com/download/8/D/D/8DD3EF84-33D7-4B37-9D61-30695B566996/VS10-KB2486994-x86.exe
- WPDT Jan-2011 update: http://download.microsoft.com/download/8/D/D/8DD3EF84-33D7-4B37-9D61-30695B566996/WindowsPhoneDeveloperResources_de_Patch1.msp

Whitepaper on Location Aware Applications for WM Devices

Maarten Struys, a former DAD MVP, has published a whitepaper on Creating Location Aware Applications for Windows Mobile Devices.

This whitepaper doesn’t only cover GPS, but Cell Tower Lookup as well. Cell Tower Lookup is based on GSM, where a position can be retrieved by the according CellID. The pros and cons of each method are covered by the whitepaper as well. A sample application is also included.

As the sample application is using the Yahoo web service for retrieving the location based on the CellID, I’d suggest to take a look at Providers like CellDB and OpenCellID. Those providers don’t only enable (after registration) to request CellID locations, but also to upload new ones.

If you are especially interested in posting new CellIDs, than you probably shall take a look at the Open Cell Client.

Windows Mobile 6.5 Dev Toolkit and Widgets

I’ve been quite astonished to find out, that the Dev Toolkit for WM 6.5 doesn’t have any documentation on how to create Widgets for WM 6.5 included.

Instead of finding it within the Dev Toolkit, an article can be found under Getting started with widgets on Windows Mobile 6.5 on MSDN. This article is supposed to be a starting point of an article series, as the information provided isn’t fully covered. Topics around the included Widget API are missing.

A small remark on the article: If you have already installed the Dev Toolkit instead of the WM 6.5 Emulator package, the description on how to use the emulator isn’t correct.

Instead of using this entry:

image

you have to use one of the Windows Mobile 6.5 Emulators, listed under the Windows Mobile 6 Professional / Standard SDK entry.

Windows Mobile 6.5 Developer Toolkit released

Yep – it is available now: The Windows Mobile 6.5 Developer Toolkit.

Developer Toolkit means that it isn’t a full blown SDK and therefore needs the Windows Mobile 6.0 SDK as a base installed.

The Toolkit includes the Windows Mobile 6.5 Emulator and is available in 7 languages (yes, already german!!!!).

You can find a brief description on the Toolkit here, or just go ahead and download it from here.

Windows Live Writer for Windows Mobile … kind of…

Ever wanted to write your blog posts from your Windows Mobile device? As there are a lot of mobile twitter apps the applications for mobile blogging are rare.

Therefore you shall take a look at Windows Live Writer for Windows Mobile, which I now take as a working name.

The name itself states that it is an application from Microsofts Windows Live Team, which ISN’T true. It isn’t associated with Microsoft in ANY way, so expect the application name to change soon. :-)

The application itself, as published on Codeplex here, looks very promising for the moment as it has started a few days ago.

The UI isn’t anything extraordinary at the moment: Plain Windows Forms controls. In my eyes this isn’t anything bad as it goes down to the basics and just serves the needs.

Looks promising – let’s see what happens in the future with this tool!

Mobile Controls from Third-Partys

I get questioned a lot of times, where to find new or different mobile controls from third partys.

First of all I’d like to point you to Resco.net. With the MobileForms Toolkit you get new forms, which are enhanced in touch functionality.

A list of all included controls including screenshots can be seen here. The toolkit itself is compatible with VS 2008 as well.

A smaller set of interesting UI components can be found at http://www.beemobile4.net/.

As it looks like this company is just starting, the included elements look promising. Especially the offer of suggesting new elements looks promising.

 

But what do you do, if you want to create your own alphablended or transparent controls?

In this case you shall have a look at Alex Yakhnins post to see, how the basics work.

If you aren’t interested in creating evereything from scratch, you are probably interested in taking a look at the AlphaMobileControls on CodePlex.

These available base elements can be used for developing more compelling controls, if needed.

The AlphaMobileControls have been shortly covered in our WebCast Series as well (unfortunatly in german only):

Windows Mobile für Profis (Teil 3 von 6) – Wege zu ansprechenden Benutzeroberflächen unter Windows Mobile: Alphablending, gradiente Farbverläufe und Transparenz

Samsung Windows Mobile SDK 1.0 available

A few weeks ago Samsung unveiled it’s Samsung Windows Mobile SDK 1.0, which you can get here.

It allows you to access phone features like Accelerometer (aka G-Sensor), notifications LEDs and haptics feedback. This is, how good device manufactures offer access to their provided functiionality to 3rd parties. Now it is up to HTC to release such an SDK as well ;).

An unofficial alternative to this is the Windows Mobile Unified Sensor SDK API on CodePlex., which can be found here. It supports the Samsung Omnia/Instinct as well as the HTC Touch Diamond/Pro.

Fehler beim Erstellen von CAB Dateien mit lokalisierten Ressourcen / Error on creating CAB Files with localized ressources

Alex Feinman wies mich gestern darauf hin, dass es anscheinend beim Erstellen von CAB Dateien mit lokalisierten Ressourcen unter Visual Studio 2008 zu einem Fehler kommt. Dies konnte ich selbst nachstellen.

Eine Variante zur Reproduktion:

1. Erstellen einer Geräteanwendung als C# oder VB.NET project
2. Hinzufügen einer neuen Ressource "Resource.en-US.resx"
3. Hinzufügen einer neuen Ressource "Resource.zh-TW.resx"
4. Hinzufügen einiger Strings zu den Ressource-Dateien
5. Erstellen des Projektes. Beachten Sie dabei, dass die entspr. erstellten Ressource-Dateien in den Unterordnern en-US and zh-TW abgelegt werden-
6. Hinzufügen eines CAB-Projektes für intelligente Geräte zur Projektmappe.
7. Hinzufügen der Projektausgabe/Primäre Ausgabe
8. Hinzufügen der Projektausgabe/Lokalisierte Ressourcen
9. Erstellen der CAB Datei. Installieren auf einem mobilen Gerät, wonach die installierten Resource-DLLs vom Zielverzeichnis des Gerätes auf die Desktop Machine kopiert werden.
10. Analysieren der DLLs mit ILDASM auf die MANIFEST/.locale. Alternativ: Reflector

Ergebnis:

Beide Ressource-DLLs sind identisch. Im konkreten Fall sind beide Dateien die der Sprache zh-TW.

Durch weitere Recherche stellte sich heraus, dass es sich hierbei um einen bereits bekannten Bug im CAB Wizard handelt. Somit geschieht dieser Fehler bei der manuellen Erstellung einer CAB Datei, als auch im Visual Studio.

 

Ilya Tumanov beschreibt hier hierzu einen Workaround:

Here’s a workaround:

1. In main project which produces resource files run a post build procedure
which would create copies of these files with unique name.

For example, “fr\CONVENO Sales.resources.dll” would be copied to
fr\fr_CONVENO Sales.resources.dll

2. In your CAB project add files with unique names instead of originals.

3. Select these files one by one, choose “Rename” in context menu and type
original name.

Here’s sample INF. Note files are unique now, but original names would be
restored on device.

Also note I’ve added files to “Application folder” so %InstallDir% macro is
actually used.

This macro can be redirected to storage card upon installation.

[Version]
Signature=”$Windows NT$”
Provider=”Microsoft”
CESignature=”$Windows CE$”

[CEStrings]
AppName=”PPC_CAB_1″
InstallDir=%CE1%\%AppName%

[Strings]
Manufacturer=”Microsoft”

[CEDevice]
VersionMin=4.0
VersionMax=5.99
BuildMax=0xE0000000

[DefaultInstall]
CEShortcuts=Shortcuts
AddReg=RegKeys
CopyFiles=Files.Common1,Files.Common2,Files.Common3

[SourceDisksNames]
1=,”Common1″,,”C:\Projects\LVTest\LVTest\bin\Debug\Fr\”
2=,”Common2″,,”C:\Projects\LVTest\LVTest\bin\Debug\”
3=,”Common3″,,”C:\Projects\LVTest\LVTest\bin\Debug\Gr\”

[SourceDisksFiles]
“fr_test.txt”=1
“LVTest.exe”=2
“gr_test.txt”=3

[DestinationDirs]
Shortcuts=0,%CE2%\Start Menu
Files.Common1=0,”%InstallDir%\Fr”
Files.Common2=0,”%InstallDir%”
Files.Common3=0,”%InstallDir%\Gr”

[Files.Common1]
“test.txt”,”fr_test.txt”,,0

[Files.Common2]
“LVTest.exe”,”LVTest.exe”,,0

[Files.Common3]
“test.txt”,”gr_test.txt”,,0

[Shortcuts]

[RegKeys]


Best regards,

Ilya

This posting is provided “AS IS” with no warranties, and confers no rights.

 

Andere Alternative: WinCE CAB Manager von ocpSoftware.

 

Angeblich ist dieser Bug schon länger bekannt, doch ein Fix ist seitens MS nicht in Sicht.

 

Danke Alex und Ilya, für die Information.

 

- English Version -

 

Alex Feinman informend me, that on creating CAB files including localized ressources under Visual Studio 2008 it can come to an error. I’ve been able to reproduce this behaviour.

One way of Reproduction:

1. Create a Form-based SmartDevice C# or VB.NET project
2. Add a new resource called Resource.en-US.resx
3. Add a new resource called Resource.zh-TW.resx
4. Add some strings to the resource files
5. Build the project. Observe that the resource DLLs are correctly
generated and placed into subdirectories en-US and zh-TW
6. Add a SmartCab deployment project to the solution.
7. Add Project Output/Primary Output
8. Add project Output/Localized Resource Assemblies
9. Build the cab file. Install it on the device and copy the resource
DLLs from the device install directory to the desktop machine.
10. Examine the DLLs with ILDASM tool checking MANIFEST/.locale. Or use Reflector.

Result:

Both resource DLLs are identical. In this case both are from the language zh-TW.

Trough further investigation it turned out, that this is a well known bug within the CAB Wizard. Therefore this bug affect manual building CAB files as well as building them from inside Visual Studio.

 

Ilya Tumanov describes here a Workaround:

Here’s a workaround:

1. In main project which produces resource files run a post build procedure
which would create copies of these files with unique name.

For example, “fr\CONVENO Sales.resources.dll” would be copied to
fr\fr_CONVENO Sales.resources.dll

2. In your CAB project add files with unique names instead of originals.

3. Select these files one by one, choose “Rename” in context menu and type
original name.

Here’s sample INF. Note files are unique now, but original names would be
restored on device.

Also note I’ve added files to “Application folder” so %InstallDir% macro is
actually used.

This macro can be redirected to storage card upon installation.

[Version]
Signature=”$Windows NT$”
Provider=”Microsoft”
CESignature=”$Windows CE$”

[CEStrings]
AppName=”PPC_CAB_1″
InstallDir=%CE1%\%AppName%

[Strings]
Manufacturer=”Microsoft”

[CEDevice]
VersionMin=4.0
VersionMax=5.99
BuildMax=0xE0000000

[DefaultInstall]
CEShortcuts=Shortcuts
AddReg=RegKeys
CopyFiles=Files.Common1,Files.Common2,Files.Common3

[SourceDisksNames]
1=,”Common1″,,”C:\Projects\LVTest\LVTest\bin\Debug\Fr\”
2=,”Common2″,,”C:\Projects\LVTest\LVTest\bin\Debug\”
3=,”Common3″,,”C:\Projects\LVTest\LVTest\bin\Debug\Gr\”

[SourceDisksFiles]
“fr_test.txt”=1
“LVTest.exe”=2
“gr_test.txt”=3

[DestinationDirs]
Shortcuts=0,%CE2%\Start Menu
Files.Common1=0,”%InstallDir%\Fr”
Files.Common2=0,”%InstallDir%”
Files.Common3=0,”%InstallDir%\Gr”

[Files.Common1]
“test.txt”,”fr_test.txt”,,0

[Files.Common2]
“LVTest.exe”,”LVTest.exe”,,0

[Files.Common3]
“test.txt”,”gr_test.txt”,,0

[Shortcuts]

[RegKeys]


Best regards,

Ilya

This posting is provided “AS IS” with no warranties, and confers no rights.

 

Alternative: WinCE CAB Manager von ocpSoftware.

 

This bug is said to be known for a longer period of time but no fix from MS it to be seen on this.

 

Thanks Alex and Ilya for this information.