How do you see the compiler command line in VB.NET?

[billben74]

Despite advances in devstudio .NET building large projects can still be
difficult.
Is there a way, perhaps using EnvDev class or some other class that
would allow output of the "command line" that is being used to compile
a VB.NET project (c.f. C++ which shows this under project
options/Linker). This would be very useful as one could
explicitly see which assemblies were being included in each project; it
would also be a good starting point to complete custom complex builds
via command line difficult in the IDE.
Thanks very much for any help.
Ben Dobson
Software Engineer
Beacon-ct.co.uk

 

[Carlos J. Quintero [.NET MVP]]

AFAIK no; you can use devenv.exe to perform command-line builds, but you
need to pass the configuration name (Debug, Release, etc.).

Maybe you can use the compiler/linker of the .NET Framework SDK.

--
Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com

 

[Ross Presser]

Despite advances in devstudio .NET building large projects can still be
difficult.
Is there a way, perhaps using EnvDev class or some other class that
would allow output of the "command line" that is being used to compile
a VB.NET project (c.f. C++ which shows this under project
options/Linker). This would be very useful as one could
explicitly see which assemblies were being included in each project; it
would also be a good starting point to complete custom complex builds
via command line difficult in the IDE.
Thanks very much for any help.
Ben Dobson
Software Engineer
Beacon-ct.co.uk

http://blogs.msdn.com/csharpfaq/archive/2004/11/30/272587.aspx

 

[billben74]

Thank you very much Carlos for taking the time to reply to my post.

Indeed one can use the vb compiler to build .net solutions. And I have
done this with simple solutions.
However what I am after are the arguments that dev studio itself
produces when it compiles a solution. I may be wrong in thinking that
dev studio uses this command line compiler itself (or something very
similar) when it compiles projects/solutions. But even if I am, I would
still like to see the command line that WOULD be neccesary to build a
solution using the command line compliler(dev studio knows how to build
a solution: I want it to tell me how it is doing this).
Why? Because we are having difficulties building complicated solutions
on different machines. If I could see a command line, like the one you
see in project/linker of C++ project, then I could (I hope) see which
dll/reference incompatability is causing a build to break.
I have read about team development at msdn, such issues as copy local
option for dlls, GAC deployment etc. But what I want is for dev studio
to tell me what it is doing (and therefore what we are doing wrong)
when it tries to build a solution.

Thank you to anyone who chips in (and thanks again to Carlos)
Ben Dobson
Software Engineer
Beacon-ct.co.uk

 

[billben74]

Thank you very much Ross.

This seems about as definative as its gets. I will now turn my
attension to NAnt to see if that will make 2003 building easier.

Thanks again.
Ben Dobson
Software Engineer
Beacon-ct.co.uk.