У меня такой вопрос.Есть ли возможность разрабатывать приложения не на локальном, а на удаленном сервере и какие
для этого нужно задать настройки ?
После задания прав доступа у меня получилось удаленно запустить проект, но когда я хотел запустить отладчик он выдал сообщение "Unable to ....Access denied", хотя я зашел на удаленный сервер администратором.
Хотел бы задать такой же вопрос. Но еще вдобавок, что проект будут писать, например 2 человека... Возможно, ли открытие проекта 2-мя пользователями одновременно???
Hello, HMVS!
You wrote on Mon, 12 Jul 2004 10:07:16 GMT:
H> Хотел бы задать такой же вопрос. Но еще вдобавок, что проект будут
H> писать, например 2 человека... Возможно, ли открытие проекта 2-мя
H> пользователями одновременно???
=========Beginning of the citation==============
Local Host vs. Remote Host
In a team development environment, the location where you initially save a
File Share Web project is extremely important. Web projects whose working
copy you save to a subdirectory of
http://localhost are referred to as local
host projects. Projects whose working copy you save to a non-local host
location (for example,
http://teamserver/webapplication1) are referred to as
remote host projects.
Local host projects are debugged locally. Remote host projects are debugged
using remote debugging. You can debug a remotely hosted Web project only on
a computer where a member of its Administrators group has given you Debugger
User permissions.
Http://localhost is the default and recommended location for Web Projects in
Visual Studio .NET. Save your project's working copy to a remote host
location for one of the following reasons:
Your personal computer cannot be used as an IIS Web server.
You need to perform pre-deployment testing and debugging on a production
server.
In most real-world situations, the production servers where a team deploys
its Web applications are significantly more powerful than their development
computers. Before deploying Web applications to such servers, you can open
them from source control on your own computer, set the working copy project
location to a virtual directory on the production server, and then run and
debug the project. On the production server, you can test for timing and
concurrency issues that might not have appeared on a less powerful desktop
computer. Applications that are developed on one computer and then debugged
on another computer whose environment approximates or is identical to that
of the production server are generally easier and less costly to deploy.
Note When one user starts debugging, the debug process locks the shared
Web server, effectively preventing other users from working on the server
until they stop debugging.
=========The end of the citation================
Posted via RSDN NNTP Server 1.9 beta
