BLOG

Category: 'dea.net'


Richard Seroter

Deploy .NET Apps to Cloud Foundry v2 with Iron Foundry

The Pivotal team recently made a significant upgrade to Cloud Foundry, changing how applications are deployed, staged, isolated, and routed. In order to work with this new model, Iron Foundry had to undergo some re-engineering work. Today, we’re proud to announce an initial release of a Cloud Foundry v2-compliant build of Iron Foundry.

Read More
Richard Seroter

Micro Iron Foundry Image Updated and Ready for Use

Micro Iron Foundry is a VM image that makes it easy to add the .NET DEA to Micro Cloud Foundry development environments. This powerful combination helps developers design their Cloud Foundry solutions locally before pushing to any number of public hosting providers.

Read More
Iron Foundry

DEA and Micro Updates.. Oh My!

Today we released the updated to the DEA (Droplet Execution Agent) and our Micro Cloud download. These updates do address some of the bugs that have been reported and also a memory leak issue with the IIS Management COM object. Download the latest DEA, Micro, and Developer tools: https://ironfoundry.org/download. Get Help: http://help.ironfoundry.org The Iron Foundry Trial environment has been updated to the latest and greatest DEA and you can sign up for FREE to try it out: https://ironfoundry.org/signup Thanks Iron Foundry Team - Bringing the Hamma!

Read More
Iron Foundry

Cloud Foundry with Iron Foundry (Windows Core) Install

image05.png

Cloud Foundry has been taking the web by storm. PaaS is growing in popularity as more developers find the disruptively positive deployment scenarios that are possible over traditional environments. Cloud Foundry, primarily centered around Linux-based PaaS, now has a sibling called Iron Foundry.

Iron Foundry is an open source project available for the Windows Server Environments with the ability to run the full spectrum of .NET Web Applications, SQL Server, and more. IronFoundry places the Microsoft tool stack on an even footing with the Linux-based stacks.

image04.png

Step 1:  Get IronFoundry Installed and Running by 

The first thing you’ll need is to be sure to get a USB Thumb Drive or some mechanism to get the .NET 4.0 & IronFoundry Software onto the Windows Server 2008 Core Instance. If you’re using a full install of Windows Server 2008 then you can use the normal means to retrieve this software. The files you’ll want on the external storage include:

  1. .NET 4.0 Framework for Server Core (dotNetFx40_Full_x86_x64_SC.exe)
  2. IronFoundry DEA Service (IronFoundry.Dea.Service.x86.msi or IronFoundry.Dea.Service.x64.msi)

Once you have the software downloaded to a medium to use, get a solid image of Windows 2008 Server Core up and running. With the Windows 2008 Server Core command prompt get the following services installed and started with the following commands:

c:UsersMyUserNamestart /w ocsetup IIS-WebServerRole

c:UsersMyUserNamestart /w ocsetup WAS-NetFxEnvironment

c:UsersMyUserNamestart /w ocsetup IIS-ISAPIExtensions

c:UsersMyUserNamestart /w ocsetup IIS-ISAPIFilter

c:UsersMyUserNamestart /w ocsetup IIS-NetFxExtensibility

c:UsersMyUserNamestart /w ocsetup IIS-ASPNET

c:UsersMyUserNamestart /w ocsetup MicrosoftWindowsPowerShell

c:UsersMyUserNamestart /w ocsetup ServerCore-WOW64

c:UsersMyUserNamestart /w ocsetup NetFx2-ServerCore

c:UsersMyUserNamestart /w ocsetup NetFx2-ServerCore-WOW64

image01.png

After these services are started, copy the software off of the USB / Storage Device that has .NET 4.0 and the IronFoundry DEA. In the below copy command, “e:” is the storage device. 

        e:copy *.* c:UsersMyUserName

Now execute the .NET 4.0 Framework (dotNetFx40_Full_x86_x64_SC.exe) for Windows 2008 Server Core.

        c:UsersMyUserNamedotNetFx40_Full_x86_x64_SC.exe

From this point a standard Windows Wizard will display to step through the rest of the .NET 4.0 Server Core Installation. The next step is to enable IIS Remote Administration: 

        c:UsersMyUserNamereg add HKEY_LOCAL_MACHINESOFTWAREMicrosoftWebManagementServer /v EnableRemoteManagement /t REG_DWORD /d 1

At this point it is actually a good idea to reboot the server to insure all the services start correctly and the registry setting takes effect. I’m sure that just simply restarting the services might work, but when playing with the registry I like to stay safe and insure everything is set and has taken effect.

After the reboot, start wmsvc.

        c:UsersMyUserNamenet start wmsvc

Now kick off the IronFoundry DEA Installation. When the wizard prompts for configuration information, enter the following:

  1. NATS Host: 10.0.0.1
  2. NATS Port: 4222
  3. App Directory: C:IronFoundryapps
  4. Droplet Directory: C:IronFoundrydroplets
  5. Install Directory: C:Program FilesIron FoundryDEA

Once the wizard is complete, then go to c:Program FilesIron FoundryDEA and run the DEA executable. This will start the IronFoundry DEA Service and insure it kicks off (self starting) anytime the server may be rebooted.

Step 2:  Deploy an ASP.NET MVC Application by 

Deploying an ASP.NET MVC application could not be easier when using Iron Foundry and the accompanying tools. There are three ways to deploy your application to Iron Foundry:

  1. Visual Studio: The Iron Foundry plugin for Visual Studio allows you to push your application to any Cloud Foundry environment supporting .NET.
  2. Cloud Foundry Explorer: The Cloud Foundry Explorer is a .NET Windows application that allows you to manage multiple cloud instances from a Windows desktop including all of the code and service deployment.
  3. Command Line (VMC): This is the command line version with all of the features that you see from the plugin and explorer.

You can download these from Iron Foundry at: https://ironfoundry.org/download 

Getting down to code a deployment… 

Lets first start out with downloading and installing the Visual Studio Plugin from Iron Foundry. Go to https://ironfoundry.org/download and download the latest. After it is downloaded double click the file and do the install.  After the install is done open up Visual Studio and go to Tools > Extension Manager > From there you should see it installed:

image00.png

Lets go ahead and write a simple ASP.NET MVC (MVC 3 is being used in this and can be downloaded here: http://www.asp.net/mvc) application by creating a simple “Hello World” application for testing. In Visual Studio do the following:

  1. Go to File > New Project
  2. Select the ASP.NET MVC 3 Web Application, set the name, location, and solution name and click “ok”
  3. On the next screen you will be prompted with the “Project Template” and you can select “Empty” and your view engine as “Razor”.

Now we have setup the project we are going to write a simple page and publish it to an Iron Foundry instance.

  1. From the Solution Explorer right click on the “Controllers” folder and go to Add > Controller.
  2. The “Add Controller” dialogue window will come up and name it “HomeController” then click the “Add” button.
  3. Next step is to add the Index View for the Home controller. You can do this by the following:
  1. Go to the “Views” folder > Create a folder called “Home” inside it
  2. Right click on the “Home” folder that was just created and Add > View. Name the View “Index.”
In the Views > Home > Index.cshtml file modify the code to be: image06.png

(NOTE: Make sure you have compiled the site at least once before pushing it live for the first time.)

With the Visual Studio Plugin from Iron Foundry it is very easy to do a deployment/update from. All you will need to do is define your Cloud Foundry instance with Iron Foundry support and then “Push” your application.

Define your Cloud Foundry instance with Iron Foundry Support:

    1. From Visual Studio Go to Tools > Cloud Foundry Explorer
    2. From Cloud Foundry Explorer click the add new cloud button.
    3. Enter in the following data:
      1. Server Name: The friendly name of the Cloud Foundry instance you plan to connect to. For this example we will use the
Iron Foundry Trial environment (api.gofoundry.net)
    1. Runtime Environment:  Select the correct runtime environment (right now it should default to: Cloud Foundry Runtime v1.0).
    2. Register/Logon Info: The Email, and Password are what you need to logon to your Cloud Foundry instance.
    3. URL: To setup the url of your cloud foundry instance do the following:
  1. Click on the “Manage Cloud…” button.
  2. From the Manage Cloud Urls… window click “Add”
  3. From the Add Cloud Url.. window type the Name and URL such as:
    1. Name: Iron Foundry Trial
    2. Url: http://api.gofoundry.net
    3. Click Ok.
  4. From the Manage Cloud Urls… window verify that your URL has been added and click ok. image07.png 
  5. Once you have entered the information correctly click to validate account and you will see an“Account Valid” message appear.
  6. Close out the Cloud Foundry Explorer window as you are now ready to push your application!
  7. Push your Application (The Cool Stuff!)

Now that you have been able to setup your Cloud Foundry instance running Iron Foundry you can now push and update your application by doing the following:

  1. Right click on your project and then go to “Push Cloud Foundry Application…
  2. image02.png
  3. From the Push Cloud Foundry Application select the correct settings:
  4. Cloud: Select the cloud you entered above.
  5. Name: Enter in any name you want for the application.
  6. URL: enter in the full url of the application. Here we will use helloworld23451.gofoundry.net.
  7. Memory Limit: Select the amount of memory you want your application to use.
  8. Instances: Select the number of instances you want your application running on.
  9. Select the services you want to bind to your application such as a database.

image03.png

Click the “Push” and it will package it up and push it live doing all the configuration of the services and application into Cloud Foundry with Iron Foundry.

Read More
Iron Foundry

The .NET DEA is now Live!

Our new DEA (Droplet Execution Agent) built using .NET is now fully available from the Iron Foundry team. After an implementation of the DEA in Ruby to run on Windows Server, we found great value in rebuilding the DEA in .NET to run natively on Windows. This will give us great flexibility in expanding the capabilities of the framework deployed to Iron Foundry. The .NET DEA enables a more stable environment and easier deployment scenario. Now the .NET DEA is ready for prime time with all functionality as the original DEA and we are very excited.

This new DEA comes with a full installer and runs as a windows service on the server. Here are the links to get you using it:

Download the .NET DEA to install

Iron Foundry has already moved to the .NET DEA in our trial environment and you will notices improvements in the application deployment and stability.

Read More
Iron Foundry

Whats next for Iron Foundry? .NET DEA and VMC in the next couple weeks

The launch of Iron Foundry this week was amazing and we want to send a sincere thanks out to the entire community. As things always do in a community process, we’ve received great suggestions, found a few hiccups, and seen some amazing engagement!  

Read More