TicketDesk 2.1.1 – Official Release

TicketDesk 2.1 LogoTicketDesk 2.1.1 has been officially released at codeplex, and the source code has been merged and pushed to the public mercurial repository.

This is a platform refresh of the TicketDesk 2 project. The source code now supports development with Visual Studio 2012, and the application has been updated to target the .Net Framwork 4.5 and Asp.net MVC 4.

The databases have not been modified, but have been verified for compatibility with SQL 2012, including localdb.

There are no new user-facing features in this release.

2 Replies to “TicketDesk 2.1.1 – Official Release”

  1. Hi,

    I’m looking to into the use of a ticketing sytem. I like TicketDesk for the clear roadmap and the platform update. I want to integrate it in a asp.net mvc4 project.

    It’s a public site with registered users. Users have several personal pages like ‘My invoices’, ‘My history’ and ‘My profile’. We just started with a new frontend and we like to have a ‘My tickets’ page as well.

    Is it possible to use TD for this and how?

    Best,
    Wouter

    1. TicketDesk 2x should be easy to integrate into another web front-end.

      I designed the system as two projects. The ticketdesk back-end is self-contained within a single class-library project, with no dependencies on any particular client front-end.

      Since you are using MVC 4, and TD2 was originally built for MVC 2, your best bet is to discard the existing UI and just write your front-end components on MVC4. This way you can follow the same conventions and practices that the rest of your front-end application uses. All of the back-end functions of TicketDesk are accessed through the “service” classes in the class library project, so you get a nice unit-of-work style pattern (technically, TD2’s pattern is closer to a transaction script pattern, but that’s not relevant).

      The back-end is setup for use with the Managed Extensibility Framework (MEF), but if you don’t want to use MEF in your application you can directly instantiate the classes from your front-end. If you are using another IoC system, you can probably use its fluent API to setup the necessary dependency injections automatically.

      Let me know if you have any specific questions.

Leave a Reply

Your email address will not be published. Required fields are marked *