DLL location when compiling

[Christina N]

When compiling my ASP.Net application, VS puts the new DLL under the local
cached directory 'VSWebCache' in stead of on the server. How can I make it
save the DLL file on the server when compiling?

I have opened the source code project through 'File - Open - Open project
from web..'

Best regards,
Christina

 

[Hermit Dave]

VSWebCache is the local directory where compilation is carried out. once its
done compiling the files the assembly file (.dll) on the server is updated.

--

Regards,

Hermit Dave
(http://hdave.blogspot.com)

 

[Christina N]

But it never updates the dll on the server. I have to manually copy it using
file explorer. Is there a project setting that tells VS to copy the file
after compiling locally?

Christina

 

[Cor Ligthert]

Christina,

But it never updates the dll on the server. I have to manually copy it using
file explorer. Is there a project setting that tells VS to copy the file
after compiling locally?

That is real not a good idea, in mainframe environments there are at least 2
seperated environments before a program goes in the production process (so
three environments).

You want to do that in one?

Cor

 

[Christina N]

Yes I am the only developer on this project, and I use 2 different
workstations, one at the office and one at home. I access the same server
from both workstations. The server is just a development server, and not an
operational server for the users.

I would like to not have to manually copy the DLL file to the server every
time I have compiled the project. I need for the current DLL file to be
there, to be able to test my programming.

Thanks for helping me.
Best regards,
Christina

 

[Cor Ligthert]

Cristina there is a button in the IDE

Project -> copy project, I never used it and it seems to be not a real
inteligent one.

However maybe it can help you in your situation.

Cor

 

[Mark Rae]

Cristina there is a button in the IDE

Project -> copy project, I never used it and it seems to be not a real
inteligent one.

Er, it's perfectly intelligent and does precisely what you'd imagine from
its name...

 

[Cor Ligthert]

Mark,

Er, it's perfectly intelligent and does precisely what you'd imagine from
its name...

I said I never used it, however I heard that it is exactly doing what is in
its name, it is copying all not only copying the changed files what I meant
with intelligent..

Cor

 

[Hermit Dave]

well i use it to copy my projects from local server to my host's server.
Take a bit of time considering that i am transferring files across adsl but
what the heck.

Cristina: I thought you used open project from web (Meaning i thought the
project was created on the Server and that you opened it from that
location.)
If that is try then you should have to copy the assemly.

if the project is on you localmachine and you manually copied a compiled
version then yes you need to use Copy Project to copy the files across

--

Regards,

Hermit Dave
(http://hdave.blogspot.com)

 

[Christina N]

The project is located on the server. I opened the project using 'File -
Open - Open project
from web..'. So I don't understand why VS stores the compiled DLL locally.
This is basically all I am asking.

Thanx,
Christina

 

[Hermit Dave]

looked up vswebcache some interesting stuff

copying a paragraph or two from the article
VSWebCache's primary purpose is to support offline development. Suppose
you're developing an app that'll be on the server at www.example.com. You
can create the application locally on your development machine-perhaps a
laptop you're using on an international flight-and later synchronize the
work you've done offline with the server. All your build files and any
support files you've added to the VS.NET project are saved locally in
C:\Documents and Settings\username\VSWebCache\example.com\MyWebApp. It
includes hidden subdirectories such as _vti_cnf and _vti_pvt. According to
the ASP.NET documentation, files are pushed to VSWebCache when you first
work offline. Then they're pushed to the server when you go back online or
synchronize the files explicitly. It works fairly similarly to how it was
supposed to work (but didn't) in Visual InterDev 6.0.

So VSWebCache is usually a good thing, because it lets you store remote
files locally so you can work on and run your site while you're offline. But
you might never work on a remote site offline. I always build my sites on
localhost, keep the files in Visual SourceSafe on a machine accessible to
both my development machine and the server, and then update the files to the
server directly from SourceSafe. I never use offline mode, and until I
researched this tip, I didn't even know where to turn it on in VS.NET. (You
select Project | Web Project | Work Offline from the VS.NET main menu.)

for more on the article
http://www.ftponline.com/vsm/2003_01/online/hottips/kiely/

there are other posts you might want to visit.
http://www.google.co.uk/search?hl=en&ie=UTF-8&q=VSWebCache+offline+project&meta=

i think you need to explicitly sync as the offline cache might be out of
sync. if you need more info. just drop in a line.
--

Regards,

Hermit Dave
(http://hdave.blogspot.com)