“There are consistencies in what we see as inconsistent”. I said this out loud today. We have an automated UI test build where all passed 2 times in a row, now without any code changes 2 have failed, with 1 failing test (a different test each time). We’ve seen this with our VM environment and Selenium tests where an element couldn’t be found or a button doesn’t click (we run the same test on small and large and the small one may fail where the large one passes => it isn’t the code 98% of the time ......
I’ve used this Nuget Packager Extension for Visual Studio with success. There are 7 well defined steps to show how to create the package. You can create a package and drop it on a network drive and you have a NuGet server! Note: Some people like to get the latest from updates to dll immediately for Continuous Integration. NuGet is a pull when you want to system. If you want updates on build, then write batch files and integrate them into your project folder. Here are a few notes I wrote for others ......
TypeScript and RequireJs work well together. Writing small modular code with Single Responsibilities (SOLID principles) is a good practice in any language and JavaScript is not an exception. AMD-Dependency Path Use amd-dependency path to include files you don’t need to use in code, but need to be loaded in order to run /// <amd-dependency path=”knockout-es5” /> Import Use import (translates to define([‘jquery’]) for adding in dependencies. Casing matters and must match the casing of the file ......