CodePlex is Dead. Long Live GitHub

I was very sad to hear about the demise of CodePlex.  I had a couple of open source projects on their site and I loved the tools provided to manage a project, especially the tight integration with Visual Studio.  But alas all good things must come to an end.  Always looking for a positive aspect to all situations, I decided that on the plus side this will force me to learn how to use Git for version control.

I have heard for some time all of the buzz around using Git but was quite content with using Team Foundation Version Control (TFVC).  But even Microsoft is embracing Git and has offered it as an option in Visual Studio for some time now and seems to get all of the new functionality when it come to version control.  Each takes a very different approach to version control, with Git being a distributed solution whereas TFVC is a centralized solution.  Microsoft has a good discussion comparing the two and when to use each in this article, Choosing the right version control for your project.   I can see where Git can be a better fit for open source projects.

So I am going to revive one of my old open source projects on CodePlex and move it to GitHub. The Project is VoiceModel and you can now find it here on GitHub.  The project has been dormant for a while but I have been getting some requests to move it to .NET Core and Visual Studio 2017.  I think that will be a great project to make the product more portable and improve performance.  With the popularity of Twilio I am also thinking about adding support for this platform.

For those not familiar with VoiceModel it is a project that makes it easier to develop VoiceXML and Tropo speech applications using ASP.Net MVC and Razor. VoiceModel uses the MVVM (Model-View-VoiceModel) design pattern to abstract the voice application to a higher level and decouples the voice user interface from the application domain and call flow. VoiceModel also supports Reusable Dialog Components (RDC) which allow you to build modules that can be reused across voice applications for increased productivity. It also has a built-in easy to use state machine that allow you to easily define your call flow. With VoiceModel you can develop your voice application once and deploy it for any VoiceXML compatible IVR or the Tropo Cloud IVR.

I am excited to revive this project and will be sharing on this blog what I learn about using GitHub for open source projects and moving VoiceModel to .NET Core.  So stay tuned.  And if you are interested in contributing visit the VoiceModel on GitHub.

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

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

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