Hi Craig,
I am not very sure what you want. But i had a recommended solution.
1) First of all, you develop everything locally.
2) Buiild it locally and this creates the dll.
3) In Visual Studio .NET - remember must build in release mode (hope for better performance).
4) When finish building, go to Project -> Copy Project
5) Type in your production site (your web server of course).
6) You can use file share (i would recommend this, can be your UNC path \\ServerName) or FrontPage (must download the latest frontpage).
7) Choose only files needed to run this application, this copies the dll needed to run.
8) Press ok, the files will be transfered from your local pc to the production web server. Make sure you had internet connection.
Then you can run already. Hope it helps.
Please correct me if i am wrong. Thanks.

Signature
Regards,
Chua Wen Ching :)
> When I do a build,Ctrl-Shift-B from Visual Studio.Net, on the production
> server, the dll gets created locally but not added to the production sites
[quoted text clipped - 7 lines]
>
> Thanks
Craig - 03 Jul 2004 14:49 GMT
That does work. But sometimes I have to do a build on the web server PC.
In the configuration manager properties Configuration Properties > Build,
The folder location is bin\. If I put a folder name before the bin\ like
test\bin\ it saves the dll in a folder on the web server. Without it saves
it
locally on my computer. Any ideas?
> Hi Craig,
>
[quoted text clipped - 31 lines]
> >
> > Thanks
I fixed it. I deleted the vswebcache files where VS has information about
projects etc. It then had to recreate the "configuration" files and all is
well. It must have gotten changed or corrupted.
> When I do a build,Ctrl-Shift-B from Visual Studio.Net, on the production
> server, the dll gets created locally but not added to the production sites
[quoted text clipped - 7 lines]
>
> Thanks