Deploying Your MVC VoiceXML Application

I found a couple of issues when deploying a VoiceXML application using MVC and VoiceModel to a hosted environment and I wanted to share the solutions here.

First you may get an error message when you try to run the application that it cannot find certain assemblies that are required for MVC.  In an earlier post titled "Using ASP.Net MVC to Create a Simple VoiceXML Application" I discuss how you have to install MVC 3 because it does not come with VS 2010 right out of the box.  Well it is currently not part of the .NET Framework either.  But there is an easy solution for including the correct assemblies as described in this blog post.  Just right click on your project and select Add Deployable Assemblies.  I dialog box will appear and select the option for ASP.NET MVC.  Now when you publish your project the appropriate assemblies will be deployed with it.

The other issue is that VoiceModel deploys shared views in the ~/tmp/Views/ directory.  When you run the application you may get an error that ASP.NET does not have the proper permission to access this directory.  The solution is simple, just give modify access to the IIS_IUSRS or ASP.NET user for this directory.

After correcting these issues I was able to run my VoiceXML application on a hosted web server without any issues.  Just make sure you hosting service support .NET 4.0.  Why would I want to put my VoiceXML application on a hosted web server?  Because I wanted to test how it worked against Voxeo's Hosted IVR service.  You can test on Voxeo's Hosted IVR service for free just as you can get a free on-premise IVR that has 2 ports for testing.  I have already discussed how to test  using the on-premise IVR (Prophecy) in "Testing Your VoiceXML App With Voxeo Prophecy".  In a future post I will show how easy it is to test in the hosted environment.

Comments

Post a Comment

Popular posts from this blog

Using Claims in ASP.NET Identity

Claims can simplify and increase the performance of authentication and authorization processes. I wrote about how you can use the roles stored as claims to eliminate back-end queries every time authorization takes place .  ASP.NET Identity has good support for claims-based identity and it creates several claims for you automatically when you create a new identity.  Here is how we create the identity for a new user during the log-in process UserManager<applicationuser> userManager = new UserManager<applicationuser>(new UserStore<applicationuser>(new SecurityContext())); ClaimsIdentity identity = userManager.CreateIdentity(user, DefaultAuthenticationTypes.ApplicationCookie); If you inspect the Claims property of ClaimsIdentity after calling CreateIdentity you will see that there are there are three or more claims. There is a claim for the user ID, user name, identity provider and one for each role assigned. So what if you want to add some more claims? Here...
Keep reading

Customizing Claims for Authorization in ASP.NET Core 2.0

Image
There have been some major changes to ASP.NET Identity with the release of Core 2.0, which you can read about here .  One of the major changes is that it does not rely on using middleware anymore to customize it.  Instead dependency injection is used by configuring via services in the ConfigureServices method of StartUp.cs .   There is not much documentation or examples on how to do this so I am going to explore how to customize ASP.NET Identity and publish some examples in this blog.  First I wanted to look at how you would add custom claims to the identity and then use those claims for authorization. To begin create a new ASP.NET Core Web Application  project in Visual Studio 2017.  Be sure to select . NET Core and ASP.NET Core 2.0 in the two drop downs at the top.  Select the template for Web Application (Model-View-Controller) and Change the Authentication to Individual User Accounts .  When the project is created you are ready to add so...
Keep reading

Seeding & Customizing ASP.NET MVC SimpleMembership

Image
In ASP.NET MVC 4 Microsoft introduced a new membership provider that is referred to as SimpleMembership.  SimpleMembership makes it easier to customize user profiles and incorporates  OAuth support.  I have seen a lot of questions on StackOverflow on how to customize SimpleMembership and seed it with data and in this post I will discuss some methods for achieving both . SimpleMembership uses Entity Framework (EF) 5 and the code-first model. To initialize the database that contains the users and roles a filter is used called  InitializeSimpleMembershipAttribute.   This attribute is decorated on the AccountController as shown here: [Authorize] [InitializeSimpleMembership] public class AccountController : Controller { ... } This is setup this way so that the initialization code is only called when accessing the actions on the AccountController .  If you look at the code for  InitializeSimpleMembershipAttribute you will see a lot of cod...
Keep reading