Serial: Java .Net Mono FreeBSD Erlang

Download it here.

Posted by 0xFF3300 at 08:26 PM | Comments (0) | TrackBack

June 04, 2004

Reflector for .NET

One of the nicer Assembly class browsers, Reflector for .NET.

"Reflector is a class browser for .NET components. It supports assembly and namespace views, type and member search, C# XML documentation viewer, call and callee graphs, IL, VB and C# disassembler, dependency trees, base type and derived type hierarchies and resource viewers. C#, Visual Basic and Delphi language syntax is supported."

Posted by 0xFF3300 at 08:38 PM | Comments (2) | TrackBack

June 03, 2004

Mono on FreeBSD, not for the Faint Hearted

Resign maintainership to ports@.  gnome@ hasn't been that active in maintaining
this, and there are some non-trivial GC problems to overcome.  Hopefully
someone will step up with a passion for .NET.

Chase the glib20 update, and bump all affected ports' PORTREVISIONs.

Whoa there, boy, that's a mighty big commit y'all have there...

Begin autotools sanitization sequence by requiring ports to explicitly
specify which version of {libtool,autoconf,automake} they need, erasing
the concept of a "system default".

For ports-in-waiting:

	USE_LIBTOOL=YES		->	USE_LIBTOOL_VER=13
	USE_AUTOCONF=YES	->	USE_AUTOCONF_VER=213
	USE_AUTOMAKE=YES	->	USE_AUTOMAKE_VER=14

Ports attempting to use the old style system after June 1st 2004 will be
sorely disappointed.

Posted by 0xFF3300 at 09:06 PM | Comments (0) | TrackBack

June 02, 2004

Software Factories

First off my response to Microsoft's 'Software Factories':

That's a good idea. The concept of giving someone patterns, frameworks, models and tools to create software is nothing new, Sun was very successful at it in the late 90s. Now Microsoft is selling the GoF spin-off patterns to it's own developer community; I must congratulate them because it's about time. Now I can communicate with other fellow .NET developers without them looking so puzzled when I mention basic software development patterns. They just go "yeah, Microsoft just came out with that this year".

The original article is here.

Read more here:
http://www.softwarefactories.com/

Posted by 0xFF3300 at 07:29 PM | Comments (1) | TrackBack

June 01, 2004

AsyncDelegate VS ThreadPool

There has been some debate about which Threading methodolgy to use when it comes to multi-threaded asynchronous applications. You could use the .NET ThreadPool or maybe use Delegates. It is really a matter of keeping track of threads and coding style.

One thing to keep in mind is wether you use Asynchronous Delegates or the System.Threading.ThreadPool class you are still:

1. Relying on the internal .NET Thread Pool.
   
2. Using the BeginInvoke and EndInvoke methods, here the WaitCallback object of QueueUserWorkItem has it's own calls:
   
   
   
   1. public virtual IAsyncResult BeginInvoke(object state, AsyncCallback callback, object object);
      
   2. public virtual void EndInvoke(IAsyncResult result);
      
   
   
3. Using Delegates.
   

QueueUserWorkItem Source: public static bool QueueUserWorkItem(WaitCallback callBack, object state) { StackCrawlMark mark1 = StackCrawlMark.LookForMyCaller; return ThreadPool.QueueUserWorkItem(callBack, state, ref mark1, true); } public static bool QueueUserWorkItem(WaitCallback callBack) { StackCrawlMark mark1 = StackCrawlMark.LookForMyCaller; return ThreadPool.QueueUserWorkItem(callBack, null, ref mark1, true); }

References:

• Asynchronus Delegates
  
• Using Delegates
  
• Toub's ManagedThreadPool
  
• Toub vs Framework