Microsoft.Net>Framework>v1.1.4322 directory so that when I run vbc.exe to
compile all the files I need they are in that directory (i.e. system.dll,
etc.).
I used to be able to, years ago, in DOS "PATH" to a directory so that it's
contents would be available no matter what directory you were in.
Can we still do this? This would be nice to avoid moving the .vb files.
thanx.Assuming you are using Windows XP follow this
- Right Click on My Computer on your Desktop.
- Click on Properties.
- Click on Advanced Tab.
- Click on Environment Variables. it will open up a dialog window.
- Under System Vars you'll find PATH, you can set it as per your
requirements.
You can do the same way with Windows 2000 also, but I m not sure abt exact
steps for now.
"Chris" wrote:
> I'm manually compiling some .vb files and I am moving them to the
> Microsoft.Net>Framework>v1.1.4322 directory so that when I run vbc.exe to
> compile all the files I need they are in that directory (i.e. system.dll,
> etc.).
> I used to be able to, years ago, in DOS "PATH" to a directory so that it's
> contents would be available no matter what directory you were in.
> Can we still do this? This would be nice to avoid moving the .vb files.
> thanx.
Are you aware of Visual Studio Command Prompt found in
Start->Programs->Microsoft Visual Studio .NET 2003->Visual Studio .NET Tools
?
Alternatively you can run batch file
"C:\Program Files\Microsoft Visual Studio .NET
2003\Common7\Tools\vsvars32.bat"
It sets up environment variables for visual studio. After this you can
compile in your work directory.
Eliyahu
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:2295EA45-EBD4-400D-A731-9EF01343A4FF@.microsoft.com...
> I'm manually compiling some .vb files and I am moving them to the
> Microsoft.Net>Framework>v1.1.4322 directory so that when I run vbc.exe to
> compile all the files I need they are in that directory (i.e. system.dll,
> etc.).
> I used to be able to, years ago, in DOS "PATH" to a directory so that it's
> contents would be available no matter what directory you were in.
> Can we still do this? This would be nice to avoid moving the .vb files.
> thanx.
no I was unaware, thank you. I saw another post where the person was using
the same path that I was so I thought that maybe that was the only way.
I like the VS command line prompt.
"Eliyahu Goldin" wrote:
> Are you aware of Visual Studio Command Prompt found in
> Start->Programs->Microsoft Visual Studio .NET 2003->Visual Studio .NET Tools
> ?
> Alternatively you can run batch file
> "C:\Program Files\Microsoft Visual Studio .NET
> 2003\Common7\Tools\vsvars32.bat"
> It sets up environment variables for visual studio. After this you can
> compile in your work directory.
> Eliyahu
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:2295EA45-EBD4-400D-A731-9EF01343A4FF@.microsoft.com...
> > I'm manually compiling some .vb files and I am moving them to the
> > Microsoft.Net>Framework>v1.1.4322 directory so that when I run vbc.exe to
> > compile all the files I need they are in that directory (i.e. system.dll,
> > etc.).
> > I used to be able to, years ago, in DOS "PATH" to a directory so that it's
> > contents would be available no matter what directory you were in.
> > Can we still do this? This would be nice to avoid moving the .vb files.
> > thanx.
>
0 comments:
Post a Comment