NANT? It sounds like you need a little monkey of a solution not a 5,000 pound elephant.
Below is a nice simple little monkey of a solution: The tedious part of compiling at the command line is referencing all the assemblies that visual studio does for you. You can store the references in a separate file though and point to them like this: vbc @vbc.rsp /target:library Foo.vb @vbc.rsp is the file that you have all the assembly references in Hmm.. the url I found this info on doesn't seem to be working at the moment: http://www.flws.com.au/showusyourcode/codeLib/code/CompileSCut.asp? catID=5 Here's the text from google's cache: NET Compilation Shortcut - referencing assemblies. Here's a neat little snippet which comes straight from the Bag-Of- Tricks dept. Anyone who's compiled a module using a command-line compiler will, likely, have been annoyed by the fact that you have to type in a reference for every satellite assembly being referenced from within the Module. For example, if I were compiling a module that used types contained within the System.Data, System.Text and System.Xml namespaces, I'd have to include a reference to each of those .dll's during compilation of my module: -------------------------------------------------------------- SAMPLE COMMAND LINE USAGE -------------------------------------------------------------- vbc /target:library /r:System.Data.dll, System.Text.dll, System.Xml.dll out:Foo.dll Foo.vb -------------------------------------------------------------- That's a lot of typing if you have to do it repeatedly. While reading Applied Microsoft .NET Framework Programming, I came across a nice little shortcut to solve this problem. You can use the @ (Specify Response File) compiler option to include one or more .rsp files that contain lists of regularly used compiler options. As per the ms docs: The compiler processes the compiler options and source code files specified in a response file as if they had been specified on the command line. To begin, simply create a text file that contains your regularaly used commands and save it with a .rsp extension: -------------------------------------------------------------- SAVE THE FOLLOWING AS vbc.rsp -------------------------------------------------------------- # command line options that the VB.NET # command line compiler VBC.exe will process # as part of every compilation, unless the # /noconfig option is specified: /r:Accessibility.dll /r:Microsoft.Vsa.dll /r:System.dll /r:System.Configuration.Install.dll /r:System.Data.dll /r:System.Design.dll /r:System.DirectoryServices.dll /r:System.Drawing.dll /r:System.Drawing.Design.dll /r:System.EnterpriseServices.dll /r:System.Management.dll /r:System.Messaging.dll /r:System.Runtime.Remoting.dll /r:System.Runtime.Serialization.Formatters.Soap.dll /r:System.Security.dll /r:System.ServiceProcess.dll /r:System.Web.dll /r:System.Web.Services.dll /r:System.XML.dll -------------------------------------------------------------- Now, when using the vbc.exe command line compiler, you can use this .rsp file to reference the .NET Framework libraries, rather than manually adding them in each time. The following sample usage would compile Foo.vb into Foo.dll. During the compilation, only assemblies references inside Foo.vb class will be recorded in the Manifest data tables for the Foo Assembly. -------------------------------------------------------------- SAMPLE COMMAND LINE USAGE -------------------------------------------------------------- vbc @vbc.rsp /target:library Foo.vb -------------------------------------------------------------- REFERENCES: http://msdn.microsoft.com/library/en- us/vblr7/html/valrfspecifyresponsefile.asp Chapter 3: Applied Microsoft .NET Framework Programming This sample has been viewed: 6783 times. --------------------------------------- END OF Article: Me again, Chris-- That Rsp file may have more assemblies referenced than you need and not have others. To find out what you need for any given assembly do this: Open the assembly that you've created in visual studio that you want your colleage to be able to update in ILDasm. Double click the Manifest Node and you'll see a list of all the assemblies that your assembly refernces. They aren't in the same format you need for the RSP but-- it still might save you some time. They'll look like this: .assembly extern System.Web { .publickeytoken = (B0 3F 5F 7F 11 D5 0A 3A ) // .?_....: .ver 1:0:5000:0 } Things might get tricky though if your colleage needs to add new assembly references .. but i guess if you have the version of the source code he's added to..then it might not be an issue. --- In [email protected], Mike Appenzellar <[EMAIL PROTECTED]> wrote: > > I code using Visual Studio but I have a co-worker that from time to > time may have to update my code behinds. What is the best/easiet way > for them to compile the code so that you see the changes? I assume > they would have to do a command line thing on the server itself? > ------------------------ Yahoo! Groups Sponsor --------------------~--> Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life. http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/saFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
