Hi, That's a very old version of CC.NET (released Feb 2006). I've had a look through the release history and it says for the 1.1 release that it breaks backwards compatibility with 1.0.1.
So, basically this means if the VSTS plug-in is developed for a later version (and I'm pretty sure it is) then it's not going to work. Is there any reason you don't want to upgrade? Craig On Jun 4, 4:27 am, fuzcase <[email protected]> wrote: > Hello, > > I am trying to use vsts to pull code into our continuous integration > process which uses VS2005 compiler. I dropped the 2005 plug-in into > the my 1.0.1 cruise control server directory, tried restarting > ccservice and get the error below. Do I need to upgrade my CCNet? Is > there a way to fix this without upgrading CCNet? > > Thanks > > Service cannot be started. > System.Reflection.ReflectionTypeLoadException: Unable to load one or > more of the requested types. Retrieve the LoaderExceptions property > for more information. > at System.Reflection.Module.GetTypesInternal(StackCrawlMark& > stackMark) > at System.Reflection.Assembly.GetTypes() > at Exortech.NetReflector.NetReflectorTypeTable.Add(Assembly > assembly) > at Exortech.NetReflector.NetReflectorTypeTable.Add(String path, > String searchPattern) > at > ThoughtWorks.CruiseControl.Core.Config.ConfigurationLoader.PopulateProjectsFromXml > (XmlDocument configXml) in d:\sourceforge\ccnet\project\core > \configuration\ConfigurationLoader.cs:line 114 > at ThoughtWorks.CruiseControl.Core.Config.ConfigurationLoader.Load > () in d:\sourceforge\ccnet\project\core\configuration > \ConfigurationLoader.cs:line 69 > at > ThoughtWorks.CruiseControl.Core.Config.ConfigurationContainer.InstanciateConfig > () in d:\sourceforge\ccnet\project\core\configuration > \ConfigurationContainer.cs:line 36 > at ThoughtWorks.CruiseControl.Core.Config.Config... > > For more information, see Help and Support Center > athttp://go.microsoft.com/fwlink/events.asp.
