Example of code analysis from StudioShell.Provider

### check-code.ps1 ###

# Run this in the Package Manager Console first – a solution must be open.
#Install-Package StudioShell.Provider

#The following should be run in the Package Manager Console in the form . pathtofilecheck-code.ps1 | out-gridview

#This is a great way of finding code entities where the filename does not match the elements name.

dir dte:/solution/codemodel -recurse | where Kind -Match ‘vs.*(Class|Enum|Interface)’ |select PSPath, Fullname, Name, Kind | % {

$toMatch = “$($_.Name).cs”;
if ($_.PSPath -NotMatch $toMatch) {
return $_
}
}

Azure Guest OS – We Need Accurate Documentation

I am not sure what is currently going on with the Azure Guest OS Availability.

Currently 3.17 is the default active one, and 3.16 is the non-default inactive one.

There are however two versions of each of 3.18 and 3.19 waiting in an inactive state.

The only source of dates for the expiry of these is:
http://msdn.microsoft.com/en-us/library/azure/ee924680.aspx

3.16 is listed as expiring yesterday (Oct 10 2014) and 3.17 is due to expire on monday (Oct 13 2014).

3.18 has already expired and 3.19 has a TBD release date.

Given that I work with a product that we like to test on an os before we actually deploy it we are in a rather difficult position. We can deploy what we have to test but will at some undefined point we will need to move to the newly released versions and retest them.

This is not a very satisfactory poisition to be in.