DLL output path on the server

C

Christina N

After I upgraded to Visual Studio .Net 2003, my Asp.net projects compile
their DLL's to my local folder only in stead of to the BIN folder on the
server where the source files reside (I open the project from the server).
So I have to copy the DLL file everytime I compile. How do I get it to use
the BIN folder on the server?

The server folder exists. And it doesn't help changing the output path in
project properties. In fact, if I change this to i.e. BIN2, then it all
works! It compiles the DLL file to a folder named BIN2 on the server. So
what's wrong with the BIN folder?

I have this problem for 2 different Asp.Net projects now.

Please help me?

Best regards
Christina
 
K

Kevin Spencer

Project Properties|Configuration Settings|Build|Output Path

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Changing the Output Path 1
Assembly Binding Path Broken? 1
1.1 vs 2.0 - Multiple DLLs? 6
Where are project files? 10
ASP.NET compile 3
Single DLL vs. Multiple DLLs 1
Web set up project problem 2
Easiest way to create a Server Control from a Web User Control 1

Top