Deployment

Labels
AJAX(112) App Studio(7) Apple(1) Application Builder(245) Application Factory(207) ASP.NET(95) ASP.NET 3.5(45) ASP.NET Code Generator(72) ASP.NET Membership(28) Azure(18) Barcode(2) Barcodes(3) BLOB(18) Business Rules(1) Business Rules/Logic(140) BYOD(13) Caching(2) Calendar(5) Charts(29) Cloud(14) Cloud On Time(2) Cloud On Time for Windows 7(2) Code Generator(54) Collaboration(11) command line(1) Conflict Detection(1) Content Management System(12) COT Tools for Excel(26) CRUD(1) Custom Actions(1) Data Aquarium Framework(122) Data Sheet(9) Data Sources(22) Database Lookups(50) Deployment(22) Designer(177) Device(1) DotNetNuke(12) EASE(20) Email(6) Features(101) Firebird(1) Form Builder(14) Globalization and Localization(6) How To(1) Hypermedia(2) Inline Editing(1) Installation(5) JavaScript(20) Kiosk(1) Low Code(3) Mac(1) Many-To-Many(4) Maps(6) Master/Detail(36) Microservices(4) Mobile(63) Mode Builder(3) Model Builder(3) MySQL(10) Native Apps(5) News(18) OAuth(8) OAuth Scopes(1) OAuth2(11) Offline(20) Offline Apps(4) Offline Sync(5) Oracle(10) PKCE(2) PostgreSQL(2) PWA(2) QR codes(2) Rapid Application Development(5) Reading Pane(2) Release Notes(179) Reports(48) REST(29) RESTful(29) RESTful Workshop(15) RFID tags(1) SaaS(7) Security(80) SharePoint(12) SPA(6) SQL Anywhere(3) SQL Server(26) SSO(1) Stored Procedure(4) Teamwork(15) Tips and Tricks(87) Tools for Excel(2) Touch UI(93) Transactions(5) Tutorials(183) Universal Windows Platform(3) User Interface(338) Video Tutorial(37) Web 2.0(100) Web App Generator(101) Web Application Generator(607) Web Form Builder(40) Web.Config(9) Workflow(28)
Archive
Blog
Deployment
Wednesday, June 18, 2014PrintSubscribe
Windows Azure Virtual Machines

One quick way of getting your app deployed online is to set up a Windows Azure Virtual Machine (VM). These VMs offer the benefit of a full-fledged Windows Server machine without the hassle of dealing with electricity and cooling costs, storing a computer on-premise, or dealing with network configuration. They also offer the additional benefits of a very fast internet connection and easy scalability. 

Getting a new Azure Virtual Machine

Let’s set up a new Azure VM for a Northwind web app created with Code On Time generator.

Navigate to http://azure.com and click on Portal in the top right corner of the screen. Enter your credentials and log in.

In the bottom left corner of the page, press New. Select Compute | Virtual Machine | Quick Create. Enter the DNS name and select the server image from the dropdown. Make sure to select the correct size as needed, as pricing is different for each one. Finally, enter the administrator credentials and select Create a Virtual Machine.

Creating a new WIndows Azure Virtual Machine.

The virtual machine will be created in a few minutes. You can watch progress by clicking on the Virtual Machines section of the site.

Waiting for the virtual machine to start.

Once the virtual machine is online, click on the VM in the list, and select CONNECT on the bottom action bar.

Downloading the rdp file for the virtual machine.

Confirm to save the downloaded *.rdp file, and open the file to start connecting to your VM using Remote Desktop Connection. Enter the previously specified username and password, and press OK.

Entering credentials for the remote virtual machine.

Confirm that you want to connect to a computer without a certificate, and you will be connected.

The virtual machine desktop accessible using Remote Desktop Connection.

Enabling HTTP Traffic to the Azure VM

In order for your application to be visible on the internet, you must enable HTTP traffic.

Switch back to the Microsoft Azure Portal. Click on the name of the virtual machine to access the properties. At the top of the page, click on ENDPOINTS tab. On the bottom action bar, press ADD.

Adding a new endpoint to the virtual machine.

Select “ADD A STAND-ALONE ENDPOINT” and press the right arrow.

Adding a new endpoint to the virtual machine.

Click on the dropdown in the NAME field and select “HTTP”. Then, press the checkmark to save the endpoint.

Adding an HTTP endpoint - TCP port 80.

You can now deploy your web app to this server.

Monday, June 16, 2014PrintSubscribe
Deployment: Prerequisites for Windows Server 2012 R2

Press the Start key on your keyboard, and start typing “features”. In the search results pane, select “Turn windows features on or off”.

Turning Windows features on in Windows Server 2012 R2.

This will open the Add Roles and Features Wizard. Press Next to continue past the Before you Begin page.

The first page of the Add Roles and Features wizard.

Select “Role-based installation” and press Next.

Selecting the installation type.

Select the local server, and press Next again.

Selecting the server to add roles to.

Check the box next to “.NET Framework 4.5 Features | ASP.NET 4.5”.

Enabling ASP.NET 4.5 Features.

Select “Web Server (IIS)” from the list, and click Add Features button to finish.

Adding the Web Server (IIS) Role.

Expand “Web Server (IIS) | Web Server | Application Development” node, and check the nodes “Application Development”, “.NET Extensibility 4.5”, “Application Initialization”, “ASP.NET 4.5”, “ISAPI Extensions”, and “ISAPI Filters”.

Enabling the required application development roles.

Continue pressing Next, then press Install when necessary. This step may take some time.

Installing the roles onto the server.

Once complete, press Close to exit the wizard.

The role installation has been completed.

Monday, June 16, 2014PrintSubscribe
Deployment: Prerequisites for Windows Server 2008 R2

Click on the Start button, and type in the word “features”. Click on “Turn Windows features on or off”.

Searching for the Server Manager.

The Server Manager will open. Right-click on Roles in the tree in the left pane, and press “Add Roles”.

Adding Roles to the server.

The Add Roles Wizard will open. Press Next to continue to the list of roles to add. Check the box next to “Application Server”. Include any required features that may be prompted.

Adding the "Application Server" role.

Press Next twice to continue to the Role Services page. Check the box next to “Web Server (IIS) Support”. Confirm to add the required roles.

Adding Web Server (IIS) Support.

Keep pressing Next until the Confirmation page appears. Select Install to add the roles to the server. This process may take some time.

Completing Installation of ASP.NET 4.5

Microsoft ASP.NET 4.5 is present on the server if all required Windows Updates have been installed. If you are using a Virtual Machine (VM) of Windows Server 2008 R2 SP1 from Windows Azure, these updates will already be installed.

Note that ASP.NET 4.5 is based on ASP.NET 4.0 and includes additional software components. The next steps do apply to ASP.NET 4.5 despite the fact that ASP.NET 4.0 folders are being referenced.

Press Start on the taskbar. Type in “cmd”, and click on the first result.

Starting command prompt.

In the prompt, type in the following for a 64-bit system:

%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i

If you using a 32-bit system, type the following:

%windir%\Microsoft.NET\Framework\v4.0.21006\aspnet_regiis.exe –i

Press Enter on the keyboard, and wait for the program to finish executing.

Installing ASP.NET 4.0.

This step will configure IIS to reference ASP.NET 4.5 libraries.