I have a Windows 8 Application that has a dozen of WCF Services that runs in the Cloud (Deployment) and on my Dev machine (Development). I switch a lot between development and deployment and I always have to change the service endpoints everytime I switch. Is there any automated way of doing this? Create a debug and the release version of the project?
Related
I created the application from the Unreal Engine. Unreal Engine, provides us the option to build the exe directly from the software. To run the application locally on any windows PC system it's working fine. But now, I want it to deploy the exe build to the AWS? What's steps/services required to get the application running online, I would like to know?
Instead of building a Windows EXE app, build a web application using .NET libs and deploy that web app to AWS Elastic Beanstalk. For more info, see https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_NET.html.
I have started developing a Web API application using .NET Core 1.1 and JetBrains Rider as IDE. Lately I have come across the need to run and debug the application hosted in a Docker container, and I wonder if anyone could share the setup on how to achieve that.
In Rider, docker support is provided by the bundled plugin, which is also used in IntelliJ IDEA. Here is a documentation: https://www.jetbrains.com/help/idea/docker.html
As for debugging, this is not supported yet, see https://youtrack.jetbrains.com/issue/RIDER-742
I have the following doubts in BizTalk deployment:
How to deploy the BizTalk application to the production server?
When I am modify the existing BizTalk application like artifacts, custom pipeline/functions, custom classes, etc., how again do I deploy the BizTalk application to the server?
I know BTDF is the one of the best tools for deploying BizTalk applications and we can deploy BizTalk application to server using it?
1. Deployment
For deployment you can use the built-in MSI generation wizard.
It means you deploy the application on a dev environment using Visual Studio, then on the admin console, export the application a MSI using the wizard.
Finally you can use that MSI to deploy the app to the Production server.
That's a two step process (Run MSI, import MSI in Bizalk Admin console).
Note that only your Biztalk assemblies are installed by the MSI.
If you use .NET assemblies in your solution, they need to be GAC'ed manually.
You will also need to restart the host instances running your Biztalk application.
See details here:
https://msdn.microsoft.com/en-ca/library/aa559168.aspx
That's a few manual steps.
Alternatively you can automate some of these steps by using the BTSTask, a command line tool included with Biztalk.
You can script all the manual steps.
Obviously it takes time to write such script, so it's only worth it if you are going to deploy many times in non-dev environments.
BTSTask reference:
https://msdn.microsoft.com/en-ca/library/aa559686.aspx
2. Redeployment
Usually you completely remove the old version and then install the new one:
Delete the application from the Biztalk Administration Console and ungac the assemblies it uses.
The whole process would look like:
1. Make sure there are no running instances in you application. You can always disable your receive location and let the running instances complete
2. Delete Biztalk application
3. UnGAC associated assemblies
4. Deploy new Biztalk application version and GAC associated assemblies
5. Restart Host Instances used by your Biztalk application
EDIT: To address OP's concern about deleting a running application:
It is indeed possible to deploy resources independently and never delete your application.
But it does not mean you will not interrupt the service.
An orchestration for example, can never be redeployed when it has running instances.
So assuming that you divided your functionality properly into applications, I find it cleaner and easier to delete the whole application than going after each resource.
Otherwise, yes you can go and replace your resources separately.
But to me it seems like an overhead caused by not having defined applications correctly.
3. BTDF
The Biztalk Deployment Framework is a good tool to have some kind of automation in your deployment without having to write the scripts yourself.
Good compromise between customization to your needs and setup time.
I have used it on a freelance project. It was very helpful because I was able to deliver a package with a only a couple of deployment instructions, and the non-techie client was able to deploy painlessly.
I need to use visual studio services (on cloud) to automate integration and release process.
I have 3 environments dev, test and deployment. I am planning to use only one branch the Dev that promotes the changes to next Env (TEST) and then to release.
Question 1:
Can I do it using one branch (Main Dev) or i need to create separate branch for each one? and how?
As far as i know that when using TFS server on premise, we should install release manager on the same machine and deployment agents on the different environments.
Question 2:
How can I automate release management using visual studio cloud services, taking into consideration that test and production environment don't use Azure services, they just use IIS to host our websites.
For the first question, the answer is YES and usually there should be only one branch for one release. The release/build that been deployed to the three environments in the release should be the same. Use the build from different branches in three environments does not make sense.
For the second question, you can use web deploy or Adding FTP Publishing to a Web Site in IIS 7 and then deploy via FTP.
You start using Release Management by creating a release definition in the RELEASE hub of your team project. A release definition specifies What to deploy - the set of artifacts that constitutes a new release, and How to deploy - the series of automation tasks that should be run in each environment. Each environment is simply a named logical entity that represents a deployment target for your release.
It seems you want to change project between environment in one release definition, which is not supported. A typical use case for Release Management:
You can get more information of Release Management at website https://msdn.microsoft.com/en-us/library/vs/alm/release/overview
Would anyone know how to configure Intellij IDEA 11 to debug a deployed "ear" application on local weblogic instance?
I am a Visual Studio guy and used to attaching VS to an local IIS process. is there something similar here?
Setup would be the same as for the Glassfish server. Remote debug may be tricky to configure, local configuration would allow you to test the changes quickly and will automatically start WebLogic with appropriate options for debugging and deployment of the artifact.