Windows XP 32 bit deployment

Question

To whom it may concern,

I am having a lot of problems deploying my Lightswitch apps.  I have decided to move away from web deployment for now, but I am also struggling to get the Desktop version deployed on a 32-bit XP Workstation.

I have tried the following:

1. Change my Configuration Manager to Any CPU

2. Rebuild to Solution (In Full)

3. I deployed it to my notebook (64 bit) and all is working 100%

4. I deployed the app to a 32-bit Windows Server and all is working 100%

5. When I try to deploy (Setup) the app to any 32-bit XP Workstation, I receive the following error: "setup is not valid WIN32 application"

Any Assistance will be appreciated.

I make use of LightSwitch V2 (Within Visual Studio 2012)

Answer 1

For points 3, 4, and 5, did you use the same published installation package without republishing in between those?

I would log a bug on the LightSwitch Connect website will all of the details that you have. It will get routed to a person who can best help figure out what the problem is.

---

Justin Anderson, LightSwitch Development Team

Answer 2

Hi Justin,

It was the same installation package.

Thank you, I will log the bug with LightSwitch Connect.

Kind Regards

Answer 3

To a Windows XP machine? Does it have Service Pack 3 installed on it?

---

Yann - LightSwitch Central - Click here for FREE Themes, Controls, Types and Commands

If you find a reply helpful, please click "Vote as Helpful", if a reply answers your question, please click "Mark as Answer"

By doing this you'll help people find answers faster.

Answer 4

Correct.  I have confirmed that service Pack 3 is installed.

Answer 5

Hmm, that was my last suggestion I'm afraid. But Justin thinks it's a bug, so we can leave it at that. If you sumbit the bug report, I'm sure the team will figure it out.

I'm sure you already know you're kind of "pushing the limit" a bit by still using Windows XP. :-P Even though XP SP3 is on the "supported" list, I don't think it'll be much of a priority, unless there's a *very* quick fix or workaround. I'm not judging you here, I'm just "managing your expectations". :-)

---

Yann - LightSwitch Central - Click here for FREE Themes, Controls, Types and Commands

If you find a reply helpful, please click "Vote as Helpful", if a reply answers your question, please click "Mark as Answer"

By doing this you'll help people find answers faster.

Answer 6

Hi Yann,

I really appreciate all your assistance and extra effort. Funny enough, I agree with you on the XP Technology, but that is what I have to work with from the Client :(

This is why I originally would have preferred the Web Route though.

I am going to park this one until I receive feedback from Microsoft, and I will re-focus on the Web Deployment to see if I can get that to work.

Kind Regards,

Answer 7

Did you ever find a solution to this?  I've got a few users who are still on XP SP3 who can't install my app, whereas everyone on Win7 can.

---

Free Visual Studio LightSwitch extensions: Elyl's Extensions

Answer 8

Cant believe this , I am currently doing deployments of an app I have created .

All the pc's are windows xp sp3 ,I had hoped it was me and not the application.

If I cant get this sorted I might as well start looking for another job !

unbelievable !

Answer 9

Sorry Ely, no resolution that I know of yet.  I have moved the users to a Web /based solution, but I still need to sort out the Integrated Security though.

I have logged the call with Microsoft as well, I will revert back as soon as I have some feedback.

Kind Regards,

Answer 10

This is indeed problematic and I will revert back if I hear from Microsoft.  I would like to suggest a Web-based implementation while they are working on the problem.

Answer 11

Thanks SpoedNick.  Unfortunately, a web based app is out of the question for me.

---

Free Visual Studio LightSwitch extensions: Elyl's Extensions

Answer 12

Web based is totally out the question for me too, I havent a clue how I am going to explain this to my client !

Answer 13

What extensions are you guys using?  I suspect the desktop apps are requiring .NET 4.5 which doesn't work on XP.

From what I can gather, my actual LS app is targeting .NET 4, but my Extension (ElylsExtensions) is forced to target .NET 4.5 as one of the LightSwitch references (Microsoft.Lightswitch.Design.Designer.dll) targets 4.5, when all the other references target v4.

One of the MS guys said he'd report this in an old thread I posted on, but I don't think anything's ever been fixed on it.  Just wondering, do your applications use my extension, or any other extension which might be making the application target .NET 4.5?

---

Free Visual Studio LightSwitch extensions: Elyl's Extensions

Answer 14

ElyIV

I do use your extensions , I will remove them and try again tomorrow.

Martin

Answer 15

Does not make any difference removing the extensions.

Just to add insult to injury a brand new project will not run on XP !

Why did I choose lightswitch as a development platform !

Microsoft you have to address this quickly please , I am in soo much sh*t with this !

Answer 16

Right

Setup.exe is not a valid Win32 application

I found this article and installed the service pack.

It now allows the app to be installed  , but it still fails when trying to run .

I can see in the article there is a dropdown for selecting the platform toolkit but i cannot see that opion in visual studio.

Answer 17

I suspect it's vslshost.exe (which is used to run the OOB app) that's preventing it from running, it probably needs to be made compatible with XP too.

What message do you see when you try to run the app?

---

Free Visual Studio LightSwitch extensions: Elyl's Extensions

Answer 18

PLATFORM VERSION INFO
 Windows    : 5.1.2600.196608 (Win32NT)
 Common Language Runtime  : 4.0.30319.1
 System.Deployment.dll   : 4.0.30319.1 (RTMRel.030319-0100)
 clr.dll    : 4.0.30319.1 (RTMRel.030319-0100)
 dfdll.dll    : 4.0.30319.1 (RTMRel.030319-0100)
 dfshim.dll    : 4.0.31106.0 (Main.031106-0000)

SOURCES
 Deployment url   : file:///F:/New%20folder/Application7.application
 Application url   : file:///F:/New%20folder/Application%20Files/Application7.exe.manifest

IDENTITIES
 Deployment Identity  : Application7.application, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0000000000000000, processorArchitecture=x86
 Application Identity  : Application7.exe, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0000000000000000, processorArchitecture=x86, type=win32

APPLICATION SUMMARY
 * Installable application.

ERROR SUMMARY
 Below is a summary of the errors, details of these errors are listed later in the log.
 * Activation of F:\New folder\Application7.application resulted in exception. Following failure messages were detected:
  +  is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)

COMPONENT STORE TRANSACTION FAILURE SUMMARY
 No transaction error was detected.

WARNINGS
 * The manifest for this application does not have a signature. Signature validation will be ignored.
 * The manifest for this application does not have a signature. Signature validation will be ignored.
 * The file named default.htm does not have a hash specified in the manifest. Hash validation will be ignored.
 * The file named web.config does not have a hash specified in the manifest. Hash validation will be ignored.

OPERATION PROGRESS STATUS
 * [14/11/2012 13:46:21] : Activation of F:\New folder\Application7.application has started.
 * [14/11/2012 13:46:21] : Processing of deployment manifest has successfully completed.
 * [14/11/2012 13:46:21] : Installation of the application has started.
 * [14/11/2012 13:46:21] : Processing of application manifest has successfully completed.
 * [14/11/2012 13:46:26] : Found compatible runtime version 4.0.30319.
 * [14/11/2012 13:46:26] : Request of trust and detection of platform is complete.
 * [14/11/2012 13:46:31] : Downloading of subscription dependencies is complete.
 * [14/11/2012 13:46:31] : Commit of the downloaded application has started.
 * [14/11/2012 13:46:36] : Installation of application has successfully completed.

ERROR DETAILS
 Following errors were detected during this operation.
 * [14/11/2012 13:46:37] System.BadImageFormatException
  -  is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.NativeMethods.CorLaunchApplication(UInt32 hostType, String applicationFullName, Int32 manifestPathsCount, String[] manifestPaths, Int32 activationDataCount, String[] activationData, PROCESS_INFORMATION processInformation)
   at System.Deployment.Application.ComponentStore.ActivateApplication(DefinitionAppId appId, String activationParameter, Boolean useActivationParameter)
   at System.Deployment.Application.SubscriptionStore.ActivateApplication(DefinitionAppId appId, String activationParameter, Boolean useActivationParameter)
   at System.Deployment.Application.ApplicationActivator.Activate(DefinitionAppId appId, AssemblyManifest appManifest, String activationParameter, Boolean useActivationParameter)
   at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
   at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

COMPONENT STORE TRANSACTION DETAILS
 * Transaction at [14/11/2012 13:46:36]
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: 66O63D1H.QTL.application
  + System.Deployment.Internal.Isolation.StoreOperationSetDeploymentMetadata
   - Status: Set
   - HRESULT: 0x0
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Application7.exe.manifest
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: vslshost.exe.config
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Microsoft.LightSwitch.SecurityData.svc
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: default.htm
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Silverlight.js
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: web\Application7.Client.xap
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: ApplicationData.svc
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: web.config
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Microsoft.LightSwitch.AppBridge.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Microsoft.LightSwitch.AppBridge.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: System.ServiceModel.DomainServices.Hosting.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: System.ServiceModel.DomainServices.Hosting.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Microsoft.Data.Edm.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Microsoft.Data.Edm.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Microsoft.LightSwitch.CodeMarker.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Microsoft.LightSwitch.CodeMarker.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Microsoft.Data.Services.Client.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Microsoft.Data.Services.Client.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Application.Server.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Application.Server.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: System.ServiceModel.DomainServices.Server.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: System.ServiceModel.DomainServices.Server.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Microsoft.LightSwitch.Server.Manifest.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Microsoft.LightSwitch.Server.Manifest.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Microsoft.LightSwitch.ExportProvider.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Microsoft.LightSwitch.ExportProvider.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Microsoft.LightSwitch.ManifestService.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Microsoft.LightSwitch.ManifestService.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: System.ServiceModel.DomainServices.EntityFramework.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: System.ServiceModel.DomainServices.EntityFramework.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Microsoft.LightSwitch.Server.Internal.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Microsoft.LightSwitch.Server.Internal.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: System.ServiceModel.PollingDuplex.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: System.ServiceModel.PollingDuplex.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Microsoft.LightSwitch.Base.Server.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Microsoft.LightSwitch.Base.Server.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: System.Spatial.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: System.Spatial.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Microsoft.LightSwitch.Server.Host.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Microsoft.LightSwitch.Server.Host.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Microsoft.LightSwitch.Extensions.Server.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Microsoft.LightSwitch.Extensions.Server.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Microsoft.LightSwitch.Server.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Microsoft.LightSwitch.Server.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Application.Common.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Application.Common.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Microsoft.WindowsAzure.ServiceRuntime.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Microsoft.WindowsAzure.ServiceRuntime.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Microsoft.LightSwitch.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Microsoft.LightSwitch.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: vslshost.exe.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: vslshost.exe
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Microsoft.Data.OData.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Microsoft.Data.OData.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: System.ServiceModel.DomainServices.Hosting.OData.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: System.ServiceModel.DomainServices.Hosting.OData.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Microsoft.Data.Services.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Microsoft.Data.Services.dll
  + System.Deployment.Internal.Isolation.StoreOperationStageComponent
   - Status: Installed
   - HRESULT: 0x0
   - Manifest: Microsoft.LightSwitch.Model.Xaml.dll.genman
  + System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
   - Status: Installed
   - HRESULT: 0x0
   - File: Microsoft.LightSwitch.Model.Xaml.dll
  + System.Deployment.Internal.Isolation.StoreOperationInstallDeployment
   - Status: Installed
   - HRESULT: 0x0
   - AppId: file:///F:/New%20folder/Application7.application#Application7.application, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0000000000000000, processorArchitecture=x86
  + System.Deployment.Internal.Isolation.StoreOperationSetDeploymentMetadata
   - Status: Set
   - HRESULT: 0x0
  + System.Deployment.Internal.Isolation.StoreTransactionOperationType (27)
   - HRESULT: 0x0

 

Answer 19

Did anyone log the Connect Bug report, as Justin suggested? If so, can you post a link to it here in this thread?

---

Yann - LightSwitch Central - Click here for FREE Themes, Controls, Types and Commands

Please click "Mark as Answer" if a reply answers your question. Please click "Vote as Helpful" , if you find a reply helpful.

By doing this you'll help others to find answers faster.

Answer 20

I have just done it again Yann, I know SpoedNick has done it as  well.

Answer 21

Someone needs to post a link to their submission, so I have something to follow up with.

---

Yann - LightSwitch Central - Click here for FREE Themes, Controls, Types and Commands

Please click "Mark as Answer" if a reply answers your question. Please click "Vote as Helpful" , if you find a reply helpful.

By doing this you'll help others to find answers faster.

Answer 22

I was looking into this yesterday and will continue to do so today.

---

David Kidder | Senior SDET | Microsoft | LightSwitch

Answer 23

Great to hear Dave! I think the guys just needed to hear that "someone" was in fact "listening".

---

Yann - LightSwitch Central - Click here for FREE Themes, Controls, Types and Commands

Please click "Mark as Answer" if a reply answers your question. Please click "Vote as Helpful" , if you find a reply helpful.

By doing this you'll help others to find answers faster.

Answer 24

Thanks Dave, Appreciated.

Answer 25

Did you install the update that was described in the comments of the blog article you mentioned:

Setup.exe is not a valid Win32 application

It is the newest version of the patch that may work for you:

Soumitra Mondal
4,019 Points 4 2 1
Recent Achievements
Blog Conversation Starter Blogger III New Blog Commentator
View Profile 7 Nov 2012 10:01 AM #
The above issue was resolved in the recent release of CTP 4. Please install the latest patch Visual Studio 2012 Update 1 CTP 4

Download vsupdate_KB2707250.exe

This would allow ClickOnce bootstrapper to run on Windows XP systems.

---

4tuneate

Answer 26

(Some of this has been mentioned earlier in the thread but I'd like to make this response as complete as possible)

2-tier desktop deployments rely on 2 exe's to run, setup.exe (the ClickOnce bootstrapper) and vslshost.exe (LightSwitch's runtime for 2-tier desktop).  For VS 2012, both of these exe's were compiled in such a way that the minimum supported OS is Vista.  Attempting to run either of them will get you the "...is not a valid win32 application" error.

To run a 2-tier desktop app, it is not necessary to run the ClickOnce bootstrapper (setup.exe) if the client machine has the necessary pre-reqs (e.g. .NET 4.0).  If the client machine has the pre-reqs, Vslshost.exe can be run directly off of a network share where the "Application Files" directory of the publish output is located.  So if  setup.exe would have been the only exe compiled in this manner, a work-around would have been, install the pre-reqs manually on client machines, and run vslshost.exe directly.  But, both exe's that shipped with VS 2012 need to run on at least Vista.

The page mentioned previously here describes the error with the ClickOnce bootstrapper and does reference a Visual Studio update that allows setup.exe to run on XP.  This update does not allow vslshost.exe to run on XP.

At this time, there is no work-around to run a 2-tier Desktop LS 2012 application on XP (the Connect bug for this is still open).

It is possible to deploy an application to IIS and configure it to run out-of-browser.  Applications deployed to IIS can be run out-of-browser on an XP client.

@ElyIV & @Nitram88 could you start another thread to discuss why this type of deployment is out of the question?

During my research of this problem I came across a couple of other forum posts with this same issue.  Folks interested in this thread may want to read the others too, just to read what has been said on the topic:

Can't run Lightswitch 2012 Programm under Windows XP

setup is not valid WIN32 application

---

David Kidder | Senior SDET | Microsoft | LightSwitch

Answer 27

It's out of the question because I don't have an IIS server to run on, and I also run .NET code on the server tier that I want running on the user's machine.

Does vslshost.exe require .NET 4.5 or anything like that which would require that it runs on Vista or higher?  If a 3-tier app could run on XP, then it would suggest that vslshost.exe has just been compiled incorrectly, with incorrect requirements.

---

Free Visual Studio LightSwitch extensions: Elyl's Extensions

Answer 28

One of the problems with making all of the "latest & greatest" technologies continue to work on XP, is that it gives people even less reason to upgrade from XP, which let's face it, is not what Microsoft want.

I'm NOT saying that I agree with that concept, just pointing it out.

---

Yann - LightSwitch Central - Click here for FREE Themes, Controls, Types and Commands

Please click "Mark as Answer" if a reply answers your question. Please click "Vote as Helpful" , if you find a reply helpful.

By doing this you'll help others to find answers faster.

Answer 29

Oh yeah, for sure.  But if you're writing LOB apps in a large corporation, there's a good chance not everyone will be on the latest OS image, regardless of whether IT want it that way.

I suspect someone's made a boob (hopefully unintentional) and set the min version to 6 when there was no need to.  The fact VS2012 update 1 contains a fix to make VC11 run on XP suggests this is the case, but while they've fixed that (making setup.exe work) they've overlooked Lightswitch.

---

Free Visual Studio LightSwitch extensions: Elyl's Extensions

Answer 30

"Someone needs to post a link to their submission, so I have something to follow up with."

Found it! Vote for it! ;)

Nitram88:
Cannot deploy lightswitch application to XP

SpoedNick:
Error when deploying a Lightswitch app to 32-bit XP

Answer 31

Can those of you affected by the issue in this thread please respond and specify the reason why using an IIS server/Desktop client (Out-of-browser) deployment is not a possibility.  So far the reasons that have been listed are:

• Uses the extension ElylsExtensions (which needs to target .NET 4.5)
• Has code in the Server project that needs to run on the client (i.e. 2-tier desktop is the only supported topology)
• No access to an IIS server.  (If this is the reason, please specify what OS your database machine is running with).

---

David Kidder | Senior SDET | Microsoft | LightSwitch

Answer 32

Hi Dave, my extension only has to target .NET 4.5 because a certain Lightswitch component was built to target that... Microsoft.LightSwitch.Design.Designer
See the first half of this thread: Upgrade to Visual Studio 2012 RTM Broke Custom Editors where Justin says he raised a bug for it, but it would seem the bug was never fixed.

Regarding IIS, my SQL server is a virtual server hosted on a larger server, it is not my server, I just have a database on it, so IIS is out of the question.  I suspect this will be more common than you think in a large corporate environment, companies don't just hand out servers like candy.

---

Free Visual Studio LightSwitch extensions: Elyl's Extensions

Answer 33

Hi Dave, my extension only has to target .NET 4.5 because a certain Lightswitch component was built to target that... Microsoft.LightSwitch.Design.Designer
See the first half of this thread: http://social.msdn.microsoft.com/Forums/en-US/lsextensibility/thread/6982d8fc-957e-482a-a79e-da46227a3db1/ where Justin says he raised a bug for it, but it would seem the bug was never fixed.

LightSwitch extensions do not target any specific version of the .NET framework, or Silverlight, etc... LightSwitch extensions are just collections of assemblies (which can target different versions of different frameworks). The individual assemblies target different versions of different frameworks. So your Design assembly targets the .NET 4.5 Framework, but the rest of your extension assemblies should be targeting .NET 4.0 and Silverlight 5.0 frameworks. Since the Design assembly does not get deployed during publish (because it should only be targeting the IDE), your published applications should not require .NET 4.5 Framework.

---

Justin Anderson, LightSwitch Development Team

Answer 34

Hi Dave,

At the moment there is no IIS available.
What I have done for now:
(based on this thread: Can't run Lightswitch 2012 Programm under Windows XP)
Change the vslshost subsystem version number from 6 to 5.01  with the following cmd:

editbin vslshost.exe /SUBSYSTEM:WINDOWS,5.01 

So you can start the application directly with vslshost.exe.

I also installed the recommended vsupdate_KB2707250 (http://www.microsoft.com/en-us/download/details.aspx?id=34818) but unfortunately I didn’t get the bootstraper working.
During the installation process it says that the application is improperly formatted.
I tried to reformat with MageUI to get a new well formatted manifest but didn’t succeed.

So for me that odd behavior seems to be a bug and I would really appreciate it if that could be fixed. I see no reason why that shouldn’t be working anymore?!

Answer 35

I tried this previously, but could not install via ClickOnce (which is a requirement) as it said the signature had been altered.

Have you tried doing this to the vslshost.exe file in the Program Files\Visual Studio 11.0\.... folder?  I suspect this is where the vslshost.exe that's copied to the Release folder comes from, and if it's patched before the build process, perhaps the ClickOnce install will work.

---

Free Visual Studio LightSwitch extensions: Elyl's Extensions

Answer 36

That will not work, it will still fail the strong name verification that ClickOnce performs.

---

David Kidder | Senior SDET | Microsoft | LightSwitch

Answer 37

That will not work, it will still fail the strong name verification that ClickOnce performs.

---

David Kidder | Senior SDET | Microsoft | LightSwitch

Answer 38

Correct, but if you resign the vslshost.exe after making the editbin changes, then it seems to work.

So, step by step, here's how I got it working.  ClickOnce installation works with this method.

All command line (administrator):

CD C:\Program Files\Microsoft Visual Studio 11.0\Common7\IDE

SN -e vslshost.exe key.snk

COPY vslshost.exe vslshost.exe.BAK

EDITBIN vslshost.exe /SUBSYSTEM:WINDOWS,5.01

"C:\Program Files\Microsoft SDKs\Windows\v8.0A\bin\NETFX 4.0 Tools\ILDASM.EXE" vslshost.exe /out:vslshost.il

C:\Windows\Microsoft.NET\Framework\v4.0.30319\ILASM.EXE vslshost.il /exe /key=key.snk /output=vslshost.exe

ERASE vslshost.il

ERASE key.snk

Some of the paths might be different on your system, so adjust accordingly.

What this does, first it extracts the public key from vslshost.exe
Then it makes a backup of vslshost.exe just in case
Then it sets vslshost.exe to be compatible with XP
Then it disassembles the vslshost.exe into ILcode
Then it reassembles the vslshost.exe, signing it with the key we previously extracted
Then it tidies up.

Once this is done, you should do a clean on any LightSwitch solutions, ensuring the /bin/Release folders are empty.  When you rebuild and publish, the new patched vslshost.exe file will be copied, and will no longer fail signature validation.

---

Free Visual Studio LightSwitch extensions: Elyl's Extensions

Answer 39

Well done Bernhard! 

I think Dave Kidder well & truly has a handle on this issue.

Any further problems, please let him know in this thread.

---

Yann - LightSwitch Central - Click here for FREE Themes, Controls, Types and Commands

Please click "Mark as Answer" if a reply answers your question. Please click "Vote as Helpful" , if you find a reply helpful.

By doing this you'll help others to find answers faster.

Answer 40

ElyIV

I tried the suggestion above , but now getting  a "cannot connect to lightswitch host error" :(

any ideas

Answer 41

Are we any further forward with this Microsoft ?

I still cannot get this published to a 32 bix xp machine using iis on the sever !!!

Martin

Answer 42

The issue will be fixed in a future release. 

The problem described in this thread does not occur on applications that are deployed to IIS.  If you cannot get the published application to work after you have deployed to IIS, please start a new thread describing what you have done and what specific errors you are getting.  The issue described in this thread is that vslshost.exe cannot be run on XP.  Applications that are deployed to IIS do not use vslshost.exe.

I have deployed a Desktop application to an Azure Web Site (which behaves exactly the same as an IIS deployment).

Anyone should be able to hit this and it should install on any machine that has the correct version of Silverlight (note that the installation will warn that the publisher cannot be verified).

http://lightswitchdesktopapplication.azurewebsites.net

Here is a screenshot from my XP machine that shows everything that is installed, along with the running application

---

David Kidder | Senior SDET | Microsoft | LightSwitch

Answer 43

Thanks Dave

I will start a new thread once i have time to check with the client again .

Martin