I am migrating existing Silverlight application in Electron and I have used existing WCF service in Electron which alredy used in silverlight app. While deploying Electron application it build .exe setup file and WCF service url is bind with .exe setup file. So I need to deploy separate .exe build for different clients (i.e. different WCF URL). Is there any way in electron to configure the WCF service so there's no need to create a separate build? Any help would be appreciated.
Related
I'm new to Jenkins, i've build the dotnet application in jenkins using microsft publish command now i want to move the exe of the application from local system (where jenkins is installed) to a actual server. how to do it? how can i move code from my local system to server. Can anyone please guide me.
One way is to zip the exe and manually deploy it on server i want to automate it.
I believe you're looking to:
Deploy your application to an Azure Virtual machine
And also automate the process
For #1: I would highly recommend using Visual Studio to publish your app to the Azure VM from your local machine for ad-hoc deployments, unless you have a hard dependency on using Jenkins.
For #2: There are a few ways in which you can do this. Here are some great resources to refer:
Deploy to a Windows Virtual Machine
Migrate an ASP.NET Web application to an Azure Virtual Machine
Deploy your ASP.NET app to Azure virtual machines by using Azure DevOps Starter
Here is another detailed blog that walks one through the CI/CD setup using Azure DevOps.
When we deploy our ASP.NET MVC application all sources, controllers, views, etc. are copied.
This is not a problem when we deploy on our server, but when we are going to deploy a copy into external servers and we don't want to share our code.
Does not exist a tool to package into libraries? .NET Core seems to deploy into DLL files, but I don't find that functionality on ASP.NET MVC.
Does not exist a tool to package into libraries?
Yes.
This is what publishing the application does - it prepares the application for deployment. When you publish, it will compile the source code and prepare only the assets your application needs to run into a deployment folder.
It compiles the source into libraries. Views are only compiled if you use the precompile views option, otherwise they are distributed as files.
Use the Publish tool to deploy to a local folder. The exact options available depend on your app type. In Solution Explorer, right-click your project and choose Publish, and then choose Folder. For more information, see Deploy to a local folder.
Tutorial: Publish your Hello World application with Visual Studio 2017
You can combine publishing with IIS Web Deploy in order to easily automate the process of deploying your web site.
I have published my MVC application and now I want to deploy the same as Azure Web App.
I want my customers to open a .bat file in which they will be prompted for Azure Publish Settings and deploy the application.
I dont want to do the below.
Deploy the solution directly from Visual Studio
Use MsDeploy or MSBuild to build the solution with publish profiles like the below and publish in Azure
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\msbuild.exe "I:\MyProject\MyProject.sln" /p:DeployOnBuild=true /p:PublishProfile=Production /p:Password=Mu50vKJfDdKfGsFvj5erC0awdxAi /p:AllowUntrustedCertificate=true /p:VisualStudioVersion=12.0
Can anyone suggest a solution ?
Thanks,
R. Venkatesan
There are several tools you can use to deploy a web app from the command line :
Azure CLI : https://azure.microsoft.com/en-us/documentation/articles/web-sites-deploy/#cli
Web Deploy Command Line : https://azure.microsoft.com/en-us/documentation/articles/web-sites-deploy/#webdeploy
I would prefer use a custom script that use Azure CLI so your customer will be asked for login to Azure instead of providing publish settings file.
Hope this helps,
Julien
I am using the web publish procedure in VS2012 to deploy my MVC 4 project to a remote IIS server. This works fine when publishing a debug configuration. However, when I try to deploy a release configuration, the build fails. The setup is that I use the MVC 4 framework, but I have all my controllers in a separate F# project. The controllers consume web services that can be accessed by using a client library that generates the clients using F# type providers. When the release configuration is building I notice multiple errors because the wcf types are no longer valid. Yet, the lib providing these types has been build al ready.
Using exactly the identical setup but changing the build configuration to debug (in the web publish dialog under settings), I can publish the solution without any problems.
Try to delete the obj folder before publishing using the release config.
I have MVC2.0 web application and I need to make an exe installer to deploy the application and the DB on the customer's server.
Is there a tool in VS2010 to do this or do I have to use a 3rd party tool?
You can create deployment package, bin deploy or simply use publish option to drop files to web server.
Here are some useful links:
Bin Deployment
VS 2010 Web Deployment
Package, One click deploy
Automating Deployment with Microsoft Web Deploy