Publishing is trying to connect using https and not http.

First, thank you for your time.

I have created a LightSwitch application which basically means it's just a silverlight asp.net application.  Within IIS I have created a very vanilla, nothing special, website on port 85.  It is not configured with 1) a virtual directory, 2) an application, 3) a certificate, 4) any ssl security settings.   During the publish wizard steps I have said No to the Secure Connections question.  I believe this to mean use http and not https.

However, when I publish to my localhost website, the output says it cannot connect to website:  https://localhost:85.  I agree!  It shouldn't be able to connect using a secure connection on port 85.  But I didn't tell it to use a secure connection.

Why is it trying to connect using https and not http?

What should I check.  I am clearly missing something.

Again, thank you for your time.
MichaelDavidCarrAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

 
SammyCommented:
On the publish wizard, what do you see in the Specify a certificate step?
Also, check the publish output step and look for the Server URL value and make sure it doesn't have https://
0
 
MichaelDavidCarrAuthor Commented:
Thank you for responding.

Here are the screen shots of the Publishing Wizard.  As you can see I am specifying that https is not required and no certificate.  The other screen shot is of the output window and there you can see that it is trying to connect using https.

I am pulling my hair out over this.  I need big help.

Thank you.

p.s.
Not that it makes any difference, but I made a slight typo in the original question.  I initially said I was using port 85 when actually I am using port 83.  oops.
vs-securitysettings.png
vs-specifycertificate.png
vs-output.png
0
 
Carl TawnSystems and Integration DeveloperCommented:
It may be down to the settings for the web app rather than the publishing option. In Visual Studio, from Project menu, select "<your application> Properties...". In the properties window that opens go to the "Web" tab then check the "Start Action" and "Servers" sections to see if either of them reference a HTTPS url.
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
MichaelDavidCarrAuthor Commented:
Thank you for your time Carl.

I was hoping there would be, but unfortunately, I could not find any references to https.

Any other suggestions?
0
 
Carl TawnSystems and Integration DeveloperCommented:
Open up the .csproj file in notepad and look for the deployment related section (should be called something like <PropertyGroup Condition="'$(Configuration)|$(Platform)' == 'DEV-Deploy|AnyCPU'">), and see what it says. There may be some reference to https in there.
0
 
MichaelDavidCarrAuthor Commented:
I have already done that.  When I initially googled this problem I found this link:
http://blogs.msdn.com/b/david_kidder/archive/2012/12/05/declaring-lightswitch-publish-wizard-bankruptcy.aspx

This post outlines how to reset all the publishing settings in the PropertyGroup section.  I did that and still to no avail!
0
 
SammyCommented:
Look for this setting in your web.config and change it to false

 
  <add key="Microsoft.LightSwitch.RequireEncryption" value="True" />

Open in new window

0
 
Carl TawnSystems and Integration DeveloperCommented:
On the "Application Server Configuration" tab of the publish wizard, double check the paths and URLs specified. If you've just specified "localhost:83" as the target URL, then it may be assuming "https", so make sure that you have explicitly stated the URL as "http://localhost:83".
0

Experts Exchange Solution brought to you by ConnectWise

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
 
MichaelDavidCarrAuthor Commented:
Sammy's advice was good too, but it was Carl's solution that did the trick.  Thank you to both of you for helping me.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.