The Weavy SDK makes it easy to extend Weavy with custom functionality. Before learning how to extend Weavy it could be useful to understand a bit more about the architecture of Weavy.
This document explains the architectural choices we made in Weavy and how it makes it possible to extend Weavy with custom functionality.
|Visual Studio Solution|
|IIS or Windows Azure|
We provide a Visual studio solution
for developers wanting to build custom functionality on top of Weavy. The solution contains a fully functional ASP.NET MVC web application
that references the
Weavy.Web assembly is an ASP.NET MVC application containing the Weavy user interface.
And although it would be technically possible to remove this dependency and build a custom user interface directly on top of
most developers will probably want to modify the existing UI instead of creating it from scratch.
Weavy.Core assembly is the deepest layer of Weavy. It contains the engine of the application and has common functionality
that even the most fundamental extensions will have to rely on. You can think of it as the base class library for Weavy.
Weavy is built on top of many existing frameworks and libraries. The most important one being ASP.NET MVC which is a modern Web development framework that encourages separation of concerns.