VoiceModel Now Available on NuGet

VoiceModel is now available on NuGet, which is the recommended method for starting a VoiceModel project in Visual Studio.  NuGet handles all of the dependencies and if you follow these instruction you will have a working "Hello World" voice application as a starting point.

To install VoiceModel with NuGet just create an Empty MVC 4 project.  Remove the Global.asax file and remove App_Start\RouteConfig.cs file. Right click on References, select "Manage NuGet Packages...", and search for VoiceModel. Select the VoiceModel package and install. When installation is complete you will have a running "Hello World" example that will run on any VoiceXML compatible IVR and Tropo.

The reason for deleting the RouteConfig.cs and Global.asax file is that NuGet does not have an easy method for modifying existing source files yet.  If you do not delete these files you will have to modify them yourself to get the application to work.  The modifications are minor.  The RouteConfig.cs file is modified so that the starting action is "StateMachine". This is useful if you are trying to do some minor testing/debugging in a web browser.  Here is the line that is modified.

defaults: new { controller = "Home", action = "StateMachine", id = UrlParameter.Optional }

Since an empty MVC 4 project is created the NuGet install will drop a source file for a Home Controller that contains the Hello World Application.

The Global.asax is modified to register VoiceModel with the application. There are only two lines added to this file. First you need to add a using statement.

using VoiceModel;

And then add the following line to the Application_Start method.

VoiceViewEngine.Register(ViewEngines.Engines);

That is all there is to getting a working VoiceModel project going.  Try it out.

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 is an ex
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 some code. For this example we are s
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 code to setup initialization which is basically
Keep reading