My other reply looks like it was lost. If this is a duplicate I apologize. It is just a matter of copying three assemblies to the jenkins build server and then using the MSTest plugin to convert into a nunit format for display purposes.
-b On Tuesday, December 4, 2012 8:05:18 PM UTC-5, Richard J wrote: > > MSTest > > It’s part of VS. > > > > *From:* jenkins...@googlegroups.com <javascript:> [mailto: > jenkins...@googlegroups.com <javascript:>] *On Behalf Of *bearrito > *Sent:* Tuesday, December 04, 2012 4:05 PM > *To:* jenkins...@googlegroups.com <javascript:> > *Subject:* Re: Open visual studio command line for build > > > > What tool are you using? > > > > TestDriven.Net, NCover or one of the Visual Studio/ Team Server offerings. > > On Monday, December 3, 2012 6:46:37 PM UTC-5, Richard J wrote: > > We use Visual Studio to run unit tests and acquire code coverage. > > > > If you know how to do that without a full VS install, please let me know. > > > > > > *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On > Behalf Of *bearrito > *Sent:* Monday, December 03, 2012 1:03 PM > *To:* jenkins...@googlegroups.com > *Subject:* Re: Open visual studio command line for build > > > > There isn't anything that can be accomplished in VS that can't be > accomplished in MSBuild. By putting VS on the build server you risk having > libraries int he GAC or in ..\Tools\ that aren't available on other > machines. > > > > -b > > On Friday, November 30, 2012 2:53:39 AM UTC-5, Vineet Hada wrote: > > Because there are some environment variables which are set while using vs > command line and not available in windows command line. > > On Nov 30, 2012 5:10 AM, "bearrito" <j.barrett...@gmail.com> wrote: > > Why would you ever want to do that? > > On Thursday, November 29, 2012 10:27:29 PM UTC-5, Vineet Hada wrote: > > Hi, > > Is there a way in jenkins to run a build in visual studio command line > rather then windows command line? > > Thanks & regards, > Vineet >
