Hi ok, you got you me scared for a moment ;-) thanks for letting us know it was a typo in your config.
with kind regards Ruben Willems On Mon, Jun 1, 2009 at 8:38 AM, BDekker <[email protected]> wrote: > > It turns out that this is the error is coming from a typo made while > updating the build publisher to do cleaning. > > On Jun 1, 1:15 am, BDekker <[email protected]> wrote: > > I am getting the following exception when upgrading from 1.4.3 to > > recent release of 1.4.4. Can anyone shed any light on what this > > exception might be or where to look to? It appears to be an error > > coming only from our projects that use our own custom tasks. > > > > Service cannot be started. > > System.Runtime.Serialization.SerializationException: Type > > 'Exortech.NetReflector.NetReflectorConverterException' in Assembly > > 'NetReflector, Version=1.1.2009.1004, Culture=neutral, > > PublicKeyToken=dbcd6104b72f39b2' is not marked as serializable. > > > > Server stack trace: > > at > > > System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize > > (Object obj, ISurrogateSelector surrogateSelector, StreamingContext > > context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter > > converter, ObjectWriter objectWriter) > > at > > System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.Serialize > > (Object obj, ISurrogateSelector surrogateSelector, StreamingContext > > context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter > > converter, ObjectWriter objectWriter) > > at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Write > > (WriteObjectInfo objectInfo, NameInfo memberNameInfo, NameInfo > > typeNameInfo) > > at > > System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize > > (Object graph, Header[... > > > > For more information, see Help and Support Center athttp:// > go.microsoft.com/fwlink/events.asp. > > > > Thanks >
