Fluentassertions : Fluent Assertions is a set of .NET extension methods that allow you to more naturally specify the expected outcome of a TDD or BDD-style test. We currently use it in all our internal and client projects, and it is used in many open-source projects. It runs on .NET 3.5, 4.0 and 4.5 (Desktop and Windows Store), Silverlight 4 and 5 and Windows Phone 7.5. And it supports the unit test frameworks NUnit, XUnit, MBUnit, Gallio and MSpec.
The System.IO namespace provides several classes that allow for various actions, such as reading and writing, to be performed on files, directories, and streams
via Common I/O Tasks.
Deploy continuously to Azure
With Visual Studio 2013 Update 4 and Visual Studio Online, you can easily set up continuous deployment to Azure VMs.
via Deploy continuously.
The basics for these tips are that you are willing to use some of your computer memory to speed things up.
The concept is to use a RAM disk for temporary files storage to speed up the development environment. I am currently using 512 memory on my 8gb Windows 8 pc for the RAM disk.
The tips originates from:
Step 1. Install Ram disk (free software):
Run ImDisk Ram Disk Configuration.
Set drive to q: and 512mb RAM disk on my 8 gb memory pc, enable “Launch at Windows Startup”.
Above: here the drive size is set to 512mb. Its changeable, its a “temp” drive. Its non persistant everything gets wiped upon system restart.
Step 2. Set asp net temp folders pointed to RAM disk:
“To speed up the first load time, you can tell IIS to store its temporary files on your RAM disk (or fastest disk) by changing the following setting in your web.config files:
You can either change your project files directly, or, if you’ve lazy and have numerous applications running on your development machine (like I do), update the system-wide web.config files. Note that you need to update this for each runtime version of the Framework and, if running a 64-bit machine, for both Framework and Framework64. On my machine, I needed to modify the following files:
Step 3. Chrome cache pointed to RAM disk:
If you use Chrome as development browser this tip helps you point out the custom cache folder and set a size.
Shortcut target value (pointed to q: drive and 100mb cache) :
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disk-cache-dir="q:\temp\chromecache" --disk-cache-size=104857600
Change HKEY_CLASSES_ROOT\ChromeHTML\shell\open\command in Windows registry to
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disk-cache-dir="q:\temp\chromecache" --disk-cache-size=104857600 -- "%1"
It feels like my computer is “snappier” and faster when surfing in Chrome. But I am not really sure if the time to render first page after build is any faster? It still takes about 1 minute after rebuild of entire solution.
Tell antivirus (for me its just windows defender) to exclude q: folder from scanning. You could also add your base projects folder and Visual Studio folders;
C:\Program Files (x86)\Microsoft Visual Studio 11.0
C:\Program Files (x86)\Microsoft Visual Studio 12.0
Create a bat file for starting Visual Studio to enforce Visual Studio temp files to q:
Bat and shortcut file for download:
Visual Studio 2013.zip
Set ReSharper temp files to use system temp as well:
Not sure if this speeds things up: (just another temp folder used by IIS):
How to, see link below.
Put new wsdl file in website root ~/Services
Goto “project” -> Service References folder ->
Select the particular web service -> right click and choose
“Update service reference”
Visual Studio builds new references against this definition and
updates some files inside the service folder *.svcinfo, Reference.cs, Reference.svcmap, app.config in the project base folder.