Not that it means a great deal every now and then you get asked for the number of lines of code in a project. Greg D answered a question on StackOverflow about this using PowerShell. I liked his answer a lot because it’s so simple. Here’s his line of PowerShell code:
(dir -include *.cs,*.xaml -recurse | select-string .).Count
I tried to update source code coming from Subversion using TortoiseSVN but got an error. I had tried to update from a folder below the root (the “Implementation” folder in this case).
Error Working copy ‘C:\source\<project name>\Implementation’ locked. Error 'C:\source\<project name>' is already locked.
Trying the TortoiseSVN > Release Lock... command did nothing in this case because I had not taken a lock out on any file. The solution was to use TortoiseSVN > Cleanup... from the root folder (‘C:\source\<project name>’ in this case.
I have 2 iPod Nanos that I use all the time and as such have to use iTunes. I’m a Windows user and I have to say that iTunes on Windows sucks. It wouldn’t be so bad if all you got was iTunes but you don’t; you also get a bunch of other services that drag your machine to its knees. In my case they are services I just don’t want, don’t need and wish would go away.
Anyway, APSDaemon.exe is one such piece of nonsense that is officially known as Apple Push. In my case it takes up so much CPU time my machine becomes totally unusable. It’s not the newest machine but it does have an AMD Athlon 64 3500+ processor. APSDaemon.exe will happily sit there chewing on 50% of my CPU. I have also noticed that when APSDaemon.exe is working hard so is Kaspersky Internet Security. Between the 2 of them 100% CPU is utilised. If I kill APSDaemon.exe Kaspersky also settles back down.
APSDaemon.exe seems to be invoked under 2 conditions, both of which must be addressed to stop the thing from starting:
iTunes will still start and run normally but ASPDaemon.exe will not. Result.
Here’s a quick reminder to self about handling SOAP faults in Silverlight applications, something that happened recently and I forgot a simple step.
Before going any further read this (it will probably answer all your questions): Creating and Handling Faults in Silverlight
Firstly, I had a WCF service that was exposing faults contracts using the [FaultContract] attribute.
[ServiceContract(Namespace = "http://some_namespace_here/ConfigurationService/2011/10/01/01", Name = "ConfigurationService")]
public interface IConfigurationService
{
[OperationContract(Name = "GetConfiguration")]
[FaultContract(typeof(MyFault))]
[FaultContract(typeof(ValidationFault))]
ConfigurationResponse GetConfiguration(ConfigurationRequest request);
}
The service was implemented along with fault types, for example:
[DataContract(Namespace = "http://some_namespace_here/WIRM/2011/10/01/01", Name = "MyFault")]
public class MyFault
{
[DataMember(IsRequired = true, Name = "FaultDetail", Order = 0)]
public string FaultDetail { get; set; }
[DataMember(IsRequired = true, Name = "FaultCode", Order = 1)]
public string FaultCode { get; set; }
}
The problem was that back in Silverlight when I was handling exceptions generated from service calls the exception didn’t have the specific detail of the fault. The trick to making this work is in the article linked to above. We chose to use the “alternative client HTTP stack” approach by adding this to App.xaml.cs:
public partial class App : Application
{
public App()
{
bool registerResult = WebRequest.RegisterPrefix("http://", WebRequestCreator.ClientHttp);
InitializeComponent();
}
}
Thereafter it was possible to get at the actual fault exceptions and take advantage of specific exception details:
private void ClientGetConfigurationCompleted(object sender, GetGetConfigurationEventArgs e)
{
if (e.Error == null)
{
// Do normal processing here...
return;
}
if (e.Error is FaultException<ValidationFault>)
{
var ex = e.Error as FaultException<ValidationFault>;
// Do stuff with validation errors (via ex.Detail)
}
if (e.Error is FaultException<MyFault>)
{
var ex = e.Error as FaultException<WirmFault>;
// Do stuff with MyFault (via ex.Detail)
}
}
That’s it.
<esri:Map x:Name="AWMap">
<esri:Map.Layers>
<esri:ArcGISDynamicMapServiceLayer
ID="BaseLayerStreets"
Url="http://servername/ArcGIS/rest/services/projectname/backgroundservicename/MapServer" />
<esri:FeatureLayer ID="Hydrants"
Url="http://servername/ArcGIS/rest/services/projectname/featureservicename/MapServer/0"
Where="1 = 1"
Mode="OnDemand"
Renderer="{StaticResource ValveRenderer}">
<esri:FeatureLayer.Clusterer>
<esri:FlareClusterer
FlareBackground="Red"
FlareForeground="White"
MaximumFlareCount="9" />
</esri:FeatureLayer.Clusterer>
</esri:FeatureLayer>
</esri:Map.Layers>
</esri:Map>
“By default, the first layer with a valid spatial reference defines the spatial reference for the map. Dynamic ArcGIS Server map and image services as well as feature layers (FeatureLayer) will be reprojected to the map's spatial reference if necessary.” - http://help.arcgis.com/en/webapi/silverlight/help/index.html#/Creating_a_map/016600000011000000/When I checked the metadata for the 2 services in the ArcGIS Services Directory I noticed that the Spatial Reference was different for the 2 services. So, I changed the XAML to something like this (note lines 2 to 8):
<esri:Map x:Name="AWMap">
<esri:Map.Extent>
<esri:Envelope XMin="111111" YMin="222222" XMax="333333" YMax="444444" >
<esri:Envelope.SpatialReference>
<esri:SpatialReference WKID="27700"/>
</esri:Envelope.SpatialReference>
</esri:Envelope>
</esri:Map.Extent>
<esri:Map.Layers>
<esri:ArcGISDynamicMapServiceLayer
ID="BaseLayerStreets"
Url="http://servername/ArcGIS/rest/services/projectname/servicename/MapServer" />
<esri:FeatureLayer ID="Hydrants"
Url="http://servername/ArcGIS/rest/services/projectname/servicename/MapServer/0"
Where="1 = 1"
Mode="OnDemand"
Renderer="{StaticResource ValveRenderer}">
<esri:FeatureLayer.Clusterer>
<esri:FlareClusterer
FlareBackground="Red"
FlareForeground="White"
MaximumFlareCount="9" />
</esri:FeatureLayer.Clusterer>
</esri:FeatureLayer>
</esri:Map.Layers>
</esri:Map>
The result was that the missing feature layer magically appeared.When working with XAML in Visual Studio 2010 I prefer to see XAML as text rather than in the design or split views. To set this as a default in Visual Studio 2010:
One thing that’s not intuitive in Visio 2007 is how to change the text on a UML activity diagram signal element. When you first drag the signal shape on to an activity diagram it displays the text “<no send action>”.
No amount of editing properties will change that unless you do some thing like the following:
1. Create a new Static Structure Diagram (if you haven’t got one already).
2. Using the UML Static Structure shape palette drag a new Signal on to the Static Structure Diagram.
3. Right-click on the signal and open Properties.
4. Change the Name to whatever you want to signal to be called.
5. Return to your Activity Diagram and using the UML Activity Diagram palette add a Signal to your activity diagram.
6. Right-click on the signal and open Properties.
7. Choose Actions from the left-hand pane.
8. Select the Send Action and choose Properties.
9. Under Send Action you can now see the signal you added to the Static Structure diagram in the Signal drop down. Select it.
10. OK to all the dialogs and now the name of the signal appears on your signal shape.
Intuitive, isn’t it!
