Posted by jpluimers on 2016/02/10
Thanks User Josh Close – Stack Overflow. for answering the below on Stack Overflow: it got my Resharper Alt-Enter key workign again.
Re-apply Visual Studio keyboard scheme:
- (VS2013 latest ReSharper)
- ReSharper > Options > Environment > Keyboard & Menus > ReSharper Platform keyboard scheme: Visual Studio > Apply Scheme > Save.
- This will reset the shortcut keys for ReSharper.
- (older versions)
- ReSharper > Options > Environment > General > Visual Studio Integration > Apply
via: visual studio – Resharper Alt Enter not working – Stack Overflow.
Posted in .NET, C#, Development, Software Development, Visual Studio 2013, Visual Studio and tools | Leave a Comment »
Posted by jpluimers on 2016/02/09
Interview with by Andrew Hunt and David Thomas, the authors of The Pragmatic Programmer: From Journeyman to Master.
Many interesting quotes including:
Most people take DRY to mean you shouldn’t duplicate code. That’s not its intention. The idea behind DRY is far grander than that.
via Orthogonality and the DRY Principle.
Posted in Agile, Development, DRY, Software Development | Leave a Comment »
Posted by jpluimers on 2016/02/08
DeployIT (now XL-Deploy) uses a Remote Plugin to connect to other systems. When conncting to Windows systems, it requires WinRM to be configured on the target.
You can either run winrm qc or winrm quickconfig (they are equivalent), then answer y to the question.
WinRM already is set up to receive requests on this machine.
WinRM is not set up to allow remote access to this machine for management.
The following changes must be made:
Create a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this
Make these changes [y/n]? y
WinRM has been updated for remote management.
Created a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this
More detailed instructions are in the overthere/README.md.
Posted in Console (command prompt window), Power User, Windows | Leave a Comment »
Posted by jpluimers on 2016/02/07
Continua CI 1.7.1 Version History
January 28th, 2016
- Update: NUnit Action now includes option to install command line via NuGet.
- Update: Set Variable action now to allows setting build variables copied from project and application variables.
- Update: Now including Inconclusive and “Not Run” tests in the unit tests tool tip on Configuration view.
- Update: PlasticSCM repository updated to deal with changes to the command line in recent versions.
- Fix: Ensure that XUnit unit test failures always include a message even when test result type is missing.
- Fix: Issue where unit test totals would be calculated incorrectly when there was more than one unit test action in a stage, some tests were shelved and the second unit test action included more than 1000 tests.
- Fix: Issue with missing TFS assembly when using the 2005 client version for a TFS repository.
- Fix: Issue where Stop button was displayed on some pages when user did not have Build.Stop permissions.
- Update: Now suppressing warning message when unit test name is truncated.
Note : You will need to update your agents after installing this build
Source: Version 1.7.1 History | Continua CI
Posted in Uncategorized | Leave a Comment »