|
Please see my new blog for more recent posts.
modified 15-Nov-14 7:19am.
|
|
|
|
|
Thank you for your very helpful articles
|
|
|
|
|
Thank you and all the best to you!
|
|
|
|
|
Well, after some initial problems with the Article Submission Wizard, I have published a new article about a project that I have named Legion. Overall I am pretty pleased with this one.
The article can be found here.
|
|
|
|
|
While writing up a new article I noticed that there isn't a 'create new' Class Diagram option in the add new item dialog for a Silverlight project.
But, as I soon discovered, it's easy to create one. First create it in a regular Desktop CLR project e.g. a regular class library project. Then, simply drag it into the Silverlight project. Type may then be happily dragged from the Solution Explorer.
Now sharing types... no, we can't do that yet unfortunately.
|
|
|
|
|
Actually, you can just right-click on the Silverlight project and pick View Class Diagram and it will create it.
“Ooh... A lesson in not changing history for Mr. I'm-my-own-grandpa” - Prof. Farnsworth
|
|
|
|
|
Now that's a better way! Thanks Dustin.
|
|
|
|
|
I've noticed that the HtmlTimer is a funny ol' thing. A static instance, present in different browsers shares state. No wonder it's deprecated eh. I'm really looking forward to SL 2.
try
{
timer.Interval = 1;
timer.Tick += timer_Tick;
timer.Start();
}
catch (AccessViolationException)
{
}
|
|
|
|
|
I've been using an HtmlTimer for synchronizing threads in Silverlight.
That class is deprecated, and the warnings were filling up my VS Error List.
To suppress them, do this:
#pragma warning disable 618
static readonly HtmlTimer timer = new HtmlTimer();
#pragma warning restore 618
|
|
|
|
|
I've just release Clog - WPF edition. here.
Only one left in the Clog series is Clog - Ajax edition.
Should be good.
|
|
|
|
|
I've decided to release another project before the Ajax version. I've got a neat idea that's got me excited.
<br/>
<hr align="left" color="black" size="1" width="200"><br/>
<b>Daniel Vaughan</b>
<small><a href="http://www.linkedin.com/in/danielvaughan" title="Daniel Vaughan LinkedIn Profile">LinkedIn Profile</a></small>
<small><a href="http://www.shelfspy.com/" title="Compare and Save">ShelfSpy</a></small>
|
|
|
|
|
Here's a little powershell script to clean a solution before you submit it to CodeProject.
get-childitem .\SilverlightEdition\Source -include *.dll -recurse | foreach ($_) {remove-item $_.fullname}
get-childitem .\SilverlightEdition\Source -include *.pdb -recurse | foreach ($_) {remove-item $_.fullname}
get-childitem .\SilverlightEdition\Source -include *.suo -force -recurse | foreach ($_) {remove-item -force $_.fullname}
get-childitem .\SilverlightEdition\Source -include *.user -recurse | foreach ($_) {remove-item $_.fullname}
get-childitem .\SilverlightEdition\Source -include *.resharper -recurse | foreach ($_) {remove-item $_.fullname}
|
|
|
|
|
For the demo app in the Clog WPF edition project that I'm working on, I've enhanced the CodeLocation class as you can see below.
By printing out the File location in the format <file name="">(line number)
Visual Studio will happily jump there for you. I trace the CodeLocation instance, and Visual Studio recognizes the string format, and provides visual recognition of it in the output window. Not a big deal, but I thought it worth mentioning.
I'll probably include this in the WPF edition article.
[DataContract]
public class CodeLocation : ICodeLocation
{
[DataMember]
public string ClassName
{
get;
set;
}
[DataMember]
public string MethodName
{
get;
set;
}
[DataMember]
public string FileName
{
get;
set;
}
[DataMember]
public int LineNumber
{
get;
set;
}
public override string ToString()
{
return string.Format("{0}({1}): {2}.{3}",
FileName, LineNumber, ClassName, MethodName);
}
}
|
|
|
|
|
Here's a tip.
To get the URL of the current page from within a WPF Browser application do this:
reference System.Deployment.dll
then
if (System.Deployment.Application.ApplicationDeployment.IsNetworkDeployed)
{
Uri uri = System.Deployment.Application.ApplicationDeployment.CurrentDeployment.ActivationUri;
}
|
|
|
|
|
I've been looking for a means to retrieve the IP Address of the client in a WCF service. Unfortunately, in .NET 3.5 Beta 2, it looks like it can't be done without using a custom channel. I did find a post though:
See here for info.
MessageProperties properties = OperationContext.Current.IncomingMessageProperties;
RemoteEndpointMessageProperty endpoint
= (RemoteEndpointMessageProperty)properties[RemoteEndpointMessageProperty.Name];
IPAddress address = endpoint.Address;
I will open this up later in Clog WPF edition.
|
|
|
|
|
I’m extremely excited about the release of Clog – Silverlight edition today.
I’ve already started work on Clog for WPF and can’t wait to get it out there. I like Clog’s extensibility. I just hope I can drum up some community support for it. It would be great to get some more Log Strategies implemented.
|
|
|
|
|
Since the development of my latest article I have made some improvements to the Silverlight edition and will produce an update upon its release. Stay tuned.
|
|
|
|
|
I've just release Clog - WPF edition. here.
Only one left in the Clog series is Clog - Ajax edition.
Should be good.
http://www.agbabanakliyat.com
|
|
|
|