1

I have created a site in Azure and downloaded the publish settings file. When I click publish in VS I get the option to select a file with publish settings but only for the ASP.NET project. More or less like so.

The problem is that I'm trying to publish a WCF library and the publish option allows only for IIS, FTP or system. I can't find an option for publishing via the settings file I've downloaded.

How can I point my WCF project to the PUBXML file?

Edit

Based on the comments and replies, I also installed ASDK. Those are the projects I can choose now.

enter image description here

Community
  • 1
  • 1
Konrad Viltersten
  • 36,151
  • 76
  • 250
  • 438

2 Answers2

1

Your best bet would be to publish your library within a Worker Role and open an http endpoint through configuration.

you can also configure ASP.NET to host your WCF endpoint. Again, just a bit of configuration needed for that.

Glenn Ferrie
  • 10,290
  • 3
  • 42
  • 73
  • Haven't used Worker Role before (up to now I've always had a website to show along with my WCFs so I never noticed that the publish differed, somehow). Is Worker Role something that's set up on Azure? There's a bunch of options on the left pane (including a cute elephant, I discovered - it wasn't there before). – Konrad Viltersten May 29 '15 at 21:02
  • You will need to install the Azure SDK (http://azure.microsoft.com/en-us/downloads/) for your IDE and then create a new "Cloud Service" project. – Glenn Ferrie May 30 '15 at 02:46
  • I think I get it but I feel a bit uncertain. Please see the addition in the original question. Is that the correct service? Why are those two different?! It seems to me that, except for some small differences, a WCF service run as a web site (the way I've done before) and run as a cloud service should be the same in their architecture. – Konrad Viltersten May 31 '15 at 20:15
1

This is what you are looking for. This screenshot is from Visual Studio Community 2013.

enter image description here

and then...

enter image description here

.. then app.config additions for your addresses, bindings, and contracts

.. then Azure Endpoint configuration

Glenn Ferrie
  • 10,290
  • 3
  • 42
  • 73
  • The pictures - definite +1. App.config I think I can manage (at least for this POC I'll be doing - it can't differ much from the way I used before deploying the service under a web application). However, you're scaring me with the last part - Azure endpoint configuration. Is it something obvious once I get there? Or is a heads-up in place? (If it's a bit complicated, I recon that some pre-reading is often of help...) – Konrad Viltersten Jun 02 '15 at 02:30