Last week recap and links:
Image courtesy of kanate / FreeDigitalPhotos.net
What are your best reads this week? Leave them in the comments below.
Our Visual Studio 2013 solution holds 283 projects. The build and load times are long. Reading some tips on the internet about speeding things up I found that the power plan of my laptop directly influences the build time.
| Operation | Power plan | Improvement | |
|---|---|---|---|
| Power saver | High performance | ||
| Clean | 00:30 | 00:15 | 50% |
| Build #1 | 02:23 | 02:16 | 5% |
| Build #2 | 00:16 | 00:08 | 50% |
| Rebuild | 02:12 | 01:44 | 25% |
Times are measured with an AddIn that writes to the output window. Not exact science, but the numbers indicate there is a direct relation between the power plan and the build time. Interesting to see that build #1 (direct after a clean) takes almost the same time for both power plans.
My laptop has an Intel Dual Core I5 with turbo boost. The power saver plan disables this. Looks like this is the main reason for the differences. Will leave it at High performance.
Today I’ve tried the Azure portal preview. The experience is different from the normal portal, but I see why Microsoft wants us to use it. Information is displayed on blades and not hidden on tabs.
I’ve created a wordpress site. Below is a combined screenshot of the steps to create it.
💡 To keep the blog free of charge go into the pricing tier and select the F1 Free option for the Web App (if not visible click view all) and Mercury for the MySQL Database.
After the site is created, wordpress will be deployed to it. Browse to the site and complete the setup with two simple steps. WordPress is up and running.
For the fun of it I added an Easter Egg plugin. Browse to erictummers.azurewebsites.net and type the Konami secret code (up,up,down,down,left,right,left,right,b,a).
I’ve taken the site down but the screenshot below shows the Easter egg(s).
Last week recap and links:
Image courtesy of kanate / FreeDigitalPhotos.net
What are your best reads this week? Leave them in the comments below.
Today I got my unit tests to crash in Visual Studio. Right after some refactoring the tests stopped working and the output window contained the following message:
The active Test Run was aborted because the execution process exited unexpectedly. To investigate further, enable local crash dumps either at the machine level or for process vstest.executionengine.x86.exe. Go to more details: http://go.microsoft.com/fwlink/?linkid=232477
Looking closer at my refactoring action I soon noted that the constructors looked odd. Below a simplified replication of the crashing code. Can you fix the code below?
[TestMethod]
public void IsWorking_DefaultConstructor_True() {
var testObject = new ClassUnderTest();
var result = testObject.IsWorking();
Assert.IsTrue(result);
}
public class ClassUnderTest {
private object SomeObject;
// existing constructor without parameters
public ClassUnderTest() : this(Environment.OSVersion) {
SomeObject = Environment.OSVersion;
}
// new constructor added
public ClassUnderTest(object someObject) : this() {
SomeObject = someObject;
}
// validate SomeObject is set
public virtual bool IsWorking() {
return SomeObject != null;
}
}
* Image courtesy of Stuart Miles / FreeDigitalPhotos.net
.NET Development by Eric 