locked
Upgrading causes COM errors to be reported during setup

    Question

  • Tablets causing a bit of a headache... couldn't resist that one liner...

    We've been using Lightswitch to target laptops and tablets. The apps are many and varied, and Lightswitch provides a great framework to package and deploy complex sophisticated apps. We then use some home grown routing and network connectivity code to synchronize with app services in the cloud.

    However have found that upgrading the installed apps is a challenge, we get a COM error when trying to perform a device update. To work around this we have had to either rename the application at build, or remove and re-install.

    We have a work around, just wondered if there are any other reports like this. We have a large >1000 number of devices in the pipeline for rollout, so a fix would be great, but we can work around it if low on the fix/release schedule.

    Thanks,

    Steve


    Steve

    Wednesday, May 02, 2012 6:48 PM

Answers

All replies

  • How is it that you have LightSwitch running on a Tablet? (other than a web page or app connecting to LightSwitch via OData)

    You have Tablets that can run Silverlight?

    If so I have never heard of a Silverlight app causing a problem on device update.


    The Visual Studio LightSwitch Marketplace

    http://LightSwitchHelpWebsite.com

    Thursday, May 03, 2012 4:03 AM
  • There are loads of tablet devices landing, durable, robust, drop proof, with SSD's rather then traditional disks. These are running Windows 7/8 and we are targeting them using LS. We are just having a few niggles around the installation process.

    The update issues seems to be around OOB applications. I've a smart guy in house trying to work around the issue, and at the same time work out what the issue is.

    We then check network connectivity and are treating the tablets as clients to our Azure Cloud server applications, online/offline functionality. Works very nicely.


    Steve

    Thursday, May 03, 2012 2:12 PM
  • this is the silverlight xap signing problem.
    Thursday, May 03, 2012 8:20 PM