OT: Nant + VB 3.0 / 3.0

  • Thread starter Thread starter Rory Becker
  • Start date Start date
R

Rory Becker

Appologies for the slightly off topic post.

I am wondering does anyone know how to make the nant system use the VBC compiler
from .net 3.0 or .net 3.5.

I'm actually skipping .net 3.0 and I'm not sure it even has a different compiler,
but the question is still valid for the .net 3.5 compiler.

Also I will need to take advantage of the multitargeting so that for now
I can have errors produced when invalid syntax is used for code targeting 2.0

I hope I am being clear.

Thanks in advance
 
Ok, I mean VB 9.0 in .Net 3.5 but you all knew that right?
It's still early (not had any coffee yet :O )
 
Rory said:
I am wondering does anyone know how to make the nant system use the VBC
compiler from .net 3.0 or .net 3.5.
Click to expand...

Do you /only/ have vbc, or do you have a full version of Studio?
I ask because it's a /lot/ easier to build stuff with the latter.

Anyway ...

Assuming that
(a) you're stuck with using vbc on its own, and
(b) I know [next to] nothing about nant,

How do you tell nant about /any/ compiler?

vbc.exe sits somewhere under the .Net Framework directory but, IIRC,
you'll have to feed it loads and loads of arguments about referenced
assemblies, which is a pain.
That's why using Visual Studio is /so/ much easier ...

devenv.com (Solution) /build (Configuration)

.... and you're done.
I'm actually skipping .net 3.0 and I'm not sure it even has a different
compiler, but the question is still valid for the .net 3.5 compiler.
Click to expand...

..Net 3.0 is just .Net 2.0 plus some Vista-specific stuff and other
goodies. IMHO, it should have been called Fx2.1. Blame the Marketing
Bods.

..Net 3.5 is the next "real" Framework release and has a whole new set of
tools and utilities, including a new compiler.
Also I will need to take advantage of the multitargeting so that for now
I can have errors produced when invalid syntax is used for code
targeting 2.0
Click to expand...

If you mean targeting a particular Framework, then you'll have to wait
for Fx3.5 and you'll /only/ be able to target Fx2.0, 3.0 and 3.5 with it
so any Fx1.0 or 1.1 [legacy??] applications will have to stay with their
respective version of VB (or VS).

HTH,
Phill W.
 
Back
Top