Jeremy Likness

6-hour training webinar: have questions about ASP.NET Web API? Whether you're brand new to the ​framework or you want to take your design to the next level, this course has the answers! Experts Christopher Harrison and Jeremy Likness walk you through Web API technology, uses, and nuances. See how the toolset makes it easy to build consumable RESTful services, accessible by a variety of clients from myriad platforms.

Get a good look at token-based security features, route attributes… Show more

6-hour training webinar: have questions about ASP.NET Web API? Whether you're brand new to the ​framework or you want to take your design to the next level, this course has the answers! Experts Christopher Harrison and Jeremy Likness walk you through Web API technology, uses, and nuances. See how the toolset makes it easy to build consumable RESTful services, accessible by a variety of clients from myriad platforms.

Get a good look at token-based security features, route attributes, error handling, and versioning. See why it is the ideal way to surface APIs that target browsers and mobile devices. Hear details on how you can easily use the built-in Visual Studio templates or explore customization, design, and implementation. Don't miss this informative and practical Web Wednesdays event! Show less

Simple, easy dependency injection framework for JavaScript. Inspired by the $injector service in the Angular framework library, I built this from scratch as a standalone experiment in dependency injection for JavaScript. It handles nested dependencies, avoids infinite recursion, takes multiple patterns for object creation, and uses annotations for dependencies that are minify-friendly. You may either set an array on the object to indicate the list of dependencies to inject into the constructor… Show more

Simple, easy dependency injection framework for JavaScript. Inspired by the $injector service in the Angular framework library, I built this from scratch as a standalone experiment in dependency injection for JavaScript. It handles nested dependencies, avoids infinite recursion, takes multiple patterns for object creation, and uses annotations for dependencies that are minify-friendly. You may either set an array on the object to indicate the list of dependencies to inject into the constructor or specify the dependencies when you add the object to the container. Show less

Almost 100 example projects for the book, "The Windows Runtime by Example."

Jounce is an open source framework for Silverlight developed by Jeremy Likness that is intended to provide basic building bocks for modular line of business applications that follow the MVVM pattern and utilize the Managed Extensibility Framework (MEF).

Jounce Quick Facts

* 100KB DLL
* Design-time and Blend friendly
* Takes a default-shared approach to MVVM artifacts
* Provides minimal scaffolding for view model binding, visual state management, dynamic XAP loading… Show more

Jounce is an open source framework for Silverlight developed by Jeremy Likness that is intended to provide basic building bocks for modular line of business applications that follow the MVVM pattern and utilize the Managed Extensibility Framework (MEF).

Jounce Quick Facts

* 100KB DLL
* Design-time and Blend friendly
* Takes a default-shared approach to MVVM artifacts
* Provides minimal scaffolding for view model binding, visual state management, dynamic XAP loading, commanding, asynchronous workflows and more
* Lightweight, flexible, and extensible Show less

Jeremy is the primary developer of Sterling, a lightweight open source NoSQL object-oriented database for .Net 4.0, Silverlight 4 and 5, and Windows Phone 7 that works with your existing class structures. Sterling supports full LINQ to Object queries over keys and indexes for fast retrieval of information from large data sets.

The goal behind Sterling is to keep it:
* Non-intrusive. You shouldn't have to change your classes just to persist them. (No awkward mapping from a class model… Show more

Jeremy is the primary developer of Sterling, a lightweight open source NoSQL object-oriented database for .Net 4.0, Silverlight 4 and 5, and Windows Phone 7 that works with your existing class structures. Sterling supports full LINQ to Object queries over keys and indexes for fast retrieval of information from large data sets.

The goal behind Sterling is to keep it:
* Non-intrusive. You shouldn't have to change your classes just to persist them. (No awkward mapping from a class model to a relational database model).
* Lightweight. As of this writing, the DLL for Sterling is under 85 Kb. No one needs to bloat their project for something as simple as persisting data.
* Flexible. While the core is light, Sterling is designed to handle any serialization task and make it ultra-easy to query databases using LINQ-to-Objects.
* Portable. Sterling runs equally well on the desktop/server .NET framework, Silverlight, and Windows Phone. Show less

RSUI engaged iVision's Application Development team to create a mobile app that not only would alert executives of a large claim, but also allow them to quickly click through to detailed documentation - without logging into a virtual private network. iVision designed the app within two months, and it was immediately put to the test when Hurricane Matthew hit in early October. RSUI executives were able to track related claims in real time using their mobile phones. Based on that successful… Show more

RSUI engaged iVision's Application Development team to create a mobile app that not only would alert executives of a large claim, but also allow them to quickly click through to detailed documentation - without logging into a virtual private network. iVision designed the app within two months, and it was immediately put to the test when Hurricane Matthew hit in early October. RSUI executives were able to track related claims in real time using their mobile phones. Based on that successful experience, users suggested enhancements - including a way to search claims by a catastrophe code. iVision developers quickly updated the app, putting even more information in every RSUI executive's pocket. Show less

Numerex Corp. engaged iVision to help solve three key problems: immediately visualize the high volume of data transmitted by network-based devices it uses to monitor and manage clients’ business assets; a real-time view of the operational health of its IoT devices, including a way to receive alerts anytime a device was behaving outside the norm; and a way to manage wireless network capacity according to demand – sending bandwidth where it was needed, as it was needed – to increase speed, reduce… Show more

Numerex Corp. engaged iVision to help solve three key problems: immediately visualize the high volume of data transmitted by network-based devices it uses to monitor and manage clients’ business assets; a real-time view of the operational health of its IoT devices, including a way to receive alerts anytime a device was behaving outside the norm; and a way to manage wireless network capacity according to demand – sending bandwidth where it was needed, as it was needed – to increase speed, reduce network consumption costs and use those savings to reduce prices for customers and increase competitive edge. Show less

The goal for the Blio project was to create a smart, intelligent e-reader that provides the same layout, fonts, and full-color images that you enjoy in the print version of your favorite titles. Blio also provides the ability to read aloud to the user, highlighting each word as it goes, so you can follow along. This and much more was accomplished by a combined Wintellect and K-NFB team using Microsoft’s latest client technologies.

The Blio project represented a challenging technical… Show more

The goal for the Blio project was to create a smart, intelligent e-reader that provides the same layout, fonts, and full-color images that you enjoy in the print version of your favorite titles. Blio also provides the ability to read aloud to the user, highlighting each word as it goes, so you can follow along. This and much more was accomplished by a combined Wintellect and K-NFB team using Microsoft’s latest client technologies.

The Blio project represented a challenging technical application for WPF and even more so for the Silverlight platform. An e-reader has a surprisingly large degree of complexity around user interaction, input, and rendering.

Rendering was one of the primary focuses for implementing the e-reader. Microsoft’s XPS (XML Paper Specification) was selected as the e-book input format. XPS was chosen for its ubiquity and portable nature. While the format is in fact portable, there were some hurdles to overcome with regard the format. For example, fonts had to be dynamically handled using in-memory assemblies to avoid loss of font formatting. Additional challenges also existed with regard to hit-testing, pagination, and memory management.

Even with these technical challenges to overcome, not only could both platforms perform, but they performed well. In fact, at one point the Silverlight implementation was out-performing the WPF application. Much care was put into using virtualizing technologies, parallel processing, and intelligent memory management, allowing Blio to deliver a very rich interactive experience without sacrificing performance. These practices are showcased by the ability to search and download, process, and play aloud books at the same time without sacrificing any performance for experience.

Much of the development success can be attributed to best practices such as a clear separation of concerns using the MVVM (Model-View-ViewModel) pattern and UI virtualization. Show less

Brought on to design and implement the Windows Phone 7 application. Key milestones included an initial kickoff meeting to discuss the project’s goals and the capabilities of the Windows Phone platform, a design effort to show how the application would function with Windows Phone controls and how it would look with Metro design principles applied, and a development cycle characterized by multiple code drops so Greenway’s business analysts could provide feedback and discuss any necessary… Show more

Brought on to design and implement the Windows Phone 7 application. Key milestones included an initial kickoff meeting to discuss the project’s goals and the capabilities of the Windows Phone platform, a design effort to show how the application would function with Windows Phone controls and how it would look with Metro design principles applied, and a development cycle characterized by multiple code drops so Greenway’s business analysts could provide feedback and discuss any necessary changes. In addition to the basic functional implementation of the application, key considerations during application development included:

* Provisioning of a core framework to address an MVVM (Model-View-ViewModel) implementation and decoupled phone-specific functionality
* Implementation of and integration with a sample version of the PrimeSUITE API to allow parallel development of the actual client-side API consumer by an external party
* Use of the DPAPI (Data Protection API) to encrypt and decrypt sensitive information being stored locally
* Implementation of a mechanism to provide automated user logout when the application has been idle for a set amount of time
* Unit testing for the ViewModels using the .Net & Visual Studio unit testing tools
* Review of the application against Windows Phone Marketplace Requirements in preparation for entry into Application Marketplace Show less

Kicked off the project by first creating the user interface (UI) and user experience (UX) for the slate application, along with the overall architecture. Design resources worked with SketchFlow artifacts, and all main UI details were created using Silverlight styles and templates. WCF was used as the main communications platform. After the design was approved, the team defined the required service interfaces and upload “touch points” between the application and Rooms to Go services. At the… Show more

Kicked off the project by first creating the user interface (UI) and user experience (UX) for the slate application, along with the overall architecture. Design resources worked with SketchFlow artifacts, and all main UI details were created using Silverlight styles and templates. WCF was used as the main communications platform. After the design was approved, the team defined the required service interfaces and upload “touch points” between the application and Rooms to Go services. At the conclusion of this work, the architecture and user interface were clearly defined, allowing development to move forward. Development work then focused on functionality allowing sales associates to choose various room components forming a list of what the customer wished to purchase. Implemented functionality included the following:
* Delivery Calendar
* Product Catalog
* Order Inquiry
* Delivery Charge Calculator
* Customer Cart and Customer Account Inquiry
* Sales Quote
* SMS Messaging
* My Leads Show less

A proof of concept was successfully implemented over several weeks and demonstrated a throughput many times in excess of the requirements. The production application was built over the course of a quarter to be fully tested and implemented in time for the 2011 tax season. The SharePoint 2010 farm provides the ability to scale out as needed to handle messages. A unique handler architecture developed by Wintellect provided the means to build distinct handlers for messages that were registered… Show more

A proof of concept was successfully implemented over several weeks and demonstrated a throughput many times in excess of the requirements. The production application was built over the course of a quarter to be fully tested and implemented in time for the 2011 tax season. The SharePoint 2010 farm provides the ability to scale out as needed to handle messages. A unique handler architecture developed by Wintellect provided the means to build distinct handlers for messages that were registered with SharePoint and used to process incoming messages. To handle new messages, the team simply writes a new handler and registers it with the SharePoint system and it is ready to go.

Nearly 100 reports were converted from the legacy Oracle system to SSRS. These reports are hosted on SSRS nodes. The partitioned SQL Server 2008 architecture allows SFS to specify new nodes as needed based on demand.

The original system processed 20 million returns a year. It peaked at 110,000 returns per hour and reports were 24 hours old. The converted system achieved up to 360,000 returns per hour and all reports are now generated near real-time.

This project demonstrated the power and scalability of the SharePoint 2010 and SQL Server 2008 technologies. The developer tooling enabled the team to write the entire system over a single quarter in time for the customer to face the 2011 tax season. The use of the Entity Framework not only accelerated development by providing a seamless integration with the database backend, but also demonstrated the maturity of the technology through the high performance and throughput it was able to achieve. The architecture will allow SFS to meet the increasing demands for tax returns in subsequent years by providing multiple tiers to scale out. The final result was over 300% improvement throughput of message processing and the elimination of the old batch-based 24-hour reporting system in favor of the new on-demand reports that are generated in real-time. Show less

On the architecture and development side, Wintellect was brought on to redesign the architecture of the Silverlight client to support Silverlight 4 and the MVVM pattern. The code was also migrated fully to Silverlight 4. Considerations for this part of the effort included:

* Provision of a core framework that addresses the MVVM implementation, modularity, and extensibility using the Managed Extensibility Framework (MEF).
* Isolated storage for caching where performance benefits were… Show more

On the architecture and development side, Wintellect was brought on to redesign the architecture of the Silverlight client to support Silverlight 4 and the MVVM pattern. The code was also migrated fully to Silverlight 4. Considerations for this part of the effort included:

* Provision of a core framework that addresses the MVVM implementation, modularity, and extensibility using the Managed Extensibility Framework (MEF).
* Isolated storage for caching where performance benefits were identified.
* Conversion of the full client application to Silverlight 4.0.
* Consideration of WCF RIA (Rich Internet Applications) Services and binary transport for the web services.
* Full unit testing using the Silverlight Unit Testing Framework.

The application relied on dozens of authenticated service calls, so the flexible architecture empowered Wintellect to build a mock service layer that enabled a fully functional runtime application even with the services offline. This helped facilitate faster development cycles and easier testing scenarios. The clear separation of concerns provided by the MVVM architecture also enabled development and design to move forward in parallel – in fact, a majority of the application was built and unit-tested before the first XAML file was generated by the design team. The designer-friendly view models and sample data enabled designers to see exactly what the application would look like in runtime using Expression Blend.

Show less

During the Vancouver Olympics in February 2010, Microsoft Corporation and NBC provided live Silverlight video streaming for the Vancouver Olympics. This effort involved a dedicated data center (“Olympic Origins servers”) combined with Internet Information Server (IIS) smooth streaming servers to provide up to 30 concurrent live video streams. The system generated over 12 petabytes of data, and at peak loads streamed 374 gigabits of video per second and handled 2.4 million pages per second… Show more

During the Vancouver Olympics in February 2010, Microsoft Corporation and NBC provided live Silverlight video streaming for the Vancouver Olympics. This effort involved a dedicated data center (“Olympic Origins servers”) combined with Internet Information Server (IIS) smooth streaming servers to provide up to 30 concurrent live video streams. The system generated over 12 petabytes of data, and at peak loads streamed 374 gigabits of video per second and handled 2.4 million pages per second. There were a total of 82 million mobile page views, 1.9 million mobile video streams, and 5,000 hours of live and on-demand video. Wintellect supported this effort by creating the health monitoring tools to monitor and ensure the reliability of the overall system.

Silverlight was used to create a configuration and monitoring application. This application would parse server XML configuration files, prompt the user for needed edits, and then batch these changes for publication to multiple remote servers.

Windows Communication Foundation (WCF) was used to facilitate communication between the Silverlight application and remote agents that were installed on each server. These provided secure encrypted links by using common protocols such as HTTPS/SSL that were firewall –friendly in the data center environment.

The WCF agents and Silverlight application were rapidly constructed due to the flexibility and capabilities offered by XAML, Silverlight and WCF. The native Silverlight support for LINQ-to-XML made it easy to parse XML documents with unknown schemas, and then use the powerful XAML-based layout mechanisms available to provide visual views of the configurations for editing and updating. PRISM was utilized to design the Health Monitoring application in a modular form in order to keep the browser footprint lightweight by dynamically loading only the modules currently needed by the operator.

The full solution was completed ahead of time and under budget. Show less