Skip to content
Vixen is a lighting sequencer for creating animated light shows.
Branch: master
Clone or download
jeffu231 Merge pull request #59 from jeffu231/VIX-2759
VIX-2759 General performance enhancements and code clean up.
Latest commit 5341195 Jun 15, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
Application/VixenApplication VIX-2759 Clean up a bunch more dead code and unused variables. This g… Jun 15, 2019
Common VIX-2759 Clean up a bunch more dead code and unused variables. This g… Jun 15, 2019
Installer 3.5u1 Release prep - Fix error in the x86 portion of the installer. Aug 15, 2018
Modules VIX-2759 Refactor the Twinkle effect to directly generate the static … Jun 15, 2019
Vixen.System VIX-2759 Initial work to tweak on some performance aspects to squeeze… Jun 13, 2019
packages VIX-2683 Initial work to support the new FSEQ v2.0 file format. This … May 15, 2019
.gitignore Merge remote-tracking branch 'remotes/jeffu231/VIX-2008' Sep 25, 2017
.tgitconfig VIX-2718 Add the TortoiseGit configuration to allow it to find the ti… Jan 20, 2019
License.txt VIX-2502 Remove the Accord libraries that are no longer needed. Aug 28, 2018
MajorVersion.txt Add MajorVersion and MinorVersion files, to be used for the automatic… Aug 23, 2014
MinorVersion.txt Update version info to the 3.6 development stream. Jan 12, 2019
Packages.dgml Merge ebrady1's Lipsync work. Untested, not compiled -- squashed merg… Jun 23, 2014
PatchVersion.txt Update version info to the 3.6 development stream. Jan 12, 2019
README.txt Update version and release notes for 3.2 update 1. Sep 15, 2015
Release Notes.txt Update release notes to prep for 3.5u4 release. Oct 29, 2018
UpdateAssemblyVersion.cmd Add shell command to automatically patch the assembly versions (as pe… Aug 23, 2014
UpdateAssemblyVersion.proj Update the installer and auto-versioner to support the 4th version di… Oct 1, 2014
UpdateAssemblyVersion.tasks Update files for the automatic build process. Aug 23, 2014
Vixen.sln Merge remote-tracking branch 'remotes/jeffu231/VIX-2635' Jan 13, 2019
Vixen.sln.DotSettings VIX-2417 Make some additional changes to the output filters to try an… Jul 13, 2018


This contains all the publicly available content for the Vixen 3 system. At present,
this includes:

- common components used by the application and modules, in /Common
- modules developed and maintained by the core team, and other contributors, in /Modules
- the main Vixen application, in /Application
- the vixen framework, in /Vixen.System
- files to build the installer, in /Installer

You should be able to open the Vixen.sln solution and have it 'magically work'.
If you have any problems, please let us know; there's quite a few small workarounds
and gotchas used to get the modules building in two different solutions.

Conventions for module development:

- The assembly name should be the name of the module (eg. TimedSequenceEditor), and
  the default namespace should be "VixenModules.<ModuleType>.<ModuleName>". For
  example, VixenModules.Editor.TimedSequenceEditor.
- The build output directory should be relative to the solution directory, in an
  'Release' directory for x86 release builds, and a 'Release64' directory for x64 release builds.
  It will also depend on the type of module. For example:
  Vixen Modules (Release):              $(SolutionDir)\Release\Modules\<ModuleType>\
  Vixen Modules (Release64):            $(SolutionDir)\Release64\Modules\<ModuleType>\
  Vixen Common assemblies (Release):    $(SolutionDir)\Release\Common\
  Vixen Common assemblies (Release64):  $(SolutionDir)\Release64\Common\
  Vixen Applications (Release):         $(SolutionDir)\Release\
  Vixen Applications (Release64):       $(SolutionDir)\Release64\

  Note: the $(SolutionDir) text will need to be edited in the .csproj file directly
        (ie. outside of Visual Studio), as VS escapes the '$()' macros.

  If you're unsure, look at another existing project, and copy the OutputPath for both
  Release and Release64, eg.:
- To reference the vixen project (or any other projects that are needed), make sure you
  add a 'project reference', and not a "normal" reference (to the binary DLL). This will
  help compatibility for other developers when used in different locations.

- When adding any other references, make sure you turn off the "Copy Local" option;
  with it on, we end up with copies of DLLs all over the place on output. :-)  If you're
  unsure, after building the solution, do a 'clean solution', and everything should be
  removed from the build output directory.

- Tabs vs. Spaces, and other formatting: Tabs are preferred, any other preferred formatting
  can be added here. However, please try to review all your own changes before committing,
  to ensure you are not making large changes to unrelated sections of code (eg. changing
  formatting in a file, or whitespace, etc.). Commits like this may be rejected.

You can’t perform that action at this time.