4 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Beth Massi commented  ·  December 12, 2011 10:30 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Hi Dave,

  Thanks for the kind words :-) and more explanation on your issue.

  So you performed all the steps listed in the deployment guide and it published successfully, so that's good. The "red-X" issue is a connectivity issue to your data sources when the application is running (more on troubleshooting here: http://blogs.msdn.com/b/lightswitch/archive/2011/09/20/diagnosing-problems-in-a-deployed-lightswitch-application-eric-erhardt.aspx)

  Can you verify this is the issue you were having? If so, sounds like what would help you is some kind of warning at publish time if the user connection strings to your data sources will work or not from the deploy server.

  Thanks,
  -Beth Massi, LightSwitch Team

• Dave Smith commented  ·  December 12, 2011 5:23 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Hi Beth, thank for the link; and can I confess being a total fanboy of yours? Your documentation is stellar and approachable ( though I really wish you'd include C# examples ) . thank you for this link... I have seen this and it is a great document... I was able to publish to IIS on the development PC, but moving it to the depoy-PC didn't result in a functional LS app. I tried both the zip-deployment option and the network option and the apps would deploy but then I'd get knee deep in Red X-land. I understand that the real problem here is my lack of experience with LS, IIS, the permission structures required, and so on. All of this can ( and will ) be overcome by me as I get deeper into it. But I'm sorry, as I'm sitting there going through Fiddler reports and searching Google for answers the fact that LS deployment has a long way to go before it can be considered stable and even remotely accessable to anyone less than a full on expert is just inescapable. Spend a few minutes searching for "Red X" or "authentication info not found" on the forums and you'll encounter a large number of conflicting ideas and advice, which is really tough to work through as what works for some folks to address issues doesnt work for others. I think there will always be some degree of wiggling and work around types of things to be done as there is a wide range of server configs out there that noone can be expect to be addressed in a single deployment routine. But when I can use the tool to do a straight deploy to a brand new IIS 7 installation on a new PC without 2 days of errors, deadends and false starts than I would repectfully suggest there is still a LOT of work that needs to be done to make deployement more straighforward, reliable and simple. Thanks again for the link and for your great ( and really appreciated! ) work within the LS community!

• Beth Massi commented  ·  December 11, 2011 9:24 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Hi Dave & Mikael,

  Have you read the deployment guide here?
  http://blogs.msdn.com/b/bethmassi/archive/2011/03/23/deployment-guide-how-to-configure-a-web-server-to-host-lightswitch-applications.aspx

  What step(s) in particular are you having trouble with? What would you specicfially improve with the deployment wizard?

  Thanks for your feedback!

  -Beth Massi, LightSwitch Team

• Mikael Dúi Bolinder commented  ·  December 10, 2011 1:08 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I agree, I know C#, but I can't deploy a LightSwitch app to my Windows Server 2008.