Re: Sharing a project

Hi,

The way we do it, is to use Visual SourceSafe on a back-end server. This integrates with Visual Studio and all devs on the team can just open the project and start playing with it, then check in when they've made their changes, we don't have "master" developers, they're all equal. When it's finished we publish to a Frontpage extended server over HTTP, not the code, just the compiled DLLs.

You can use Frontpage 2003 to author in the same web as a VS2005 web application but you should separate web authoring from web apps with a well thought out folder structure and app boundaries on IIS. Note however, that Frontpage is now dead, and it's unclear how it will work in future; Sharepoint designer may only work on SharePoint servers (I don't know yet) and Expression Web won't be included on MSDN or Volume License (according to Microsoft in Jan 07, but who knows in future?), and Visual Studio can't target SharePoint - in short it's a total mess.

I advise you get a server admin to set it up for you.

AspDotNetDeveloper wrote:
I've been using VS .Net for quite a while now, but one thing I've never gotten around to figuring out, is how to share a project file between multiple developers. With check-in/check-out enabled, it checks the file out when you are adding pages, or want to save the project. How do I manage multiple developers editing the same project? Should one person be the master project updater, and add files for people through a request type setup?

I'm working with 2 additional developers now, so it's starting to become an issue, since I'd like them to use VS .Net also, but I've been having them use FP 2003 to do their editing, since they can do it without having to open the project file, while I'm in there working on things.

Perhaps it's how I have things setup... I have one project file for the root web, and not multiple project files per folder, since I'm doing a lot of traditional ASP maintenance / development also using VS .Net 2003.

Any tips / ideas would be appreciated. I don't use any versioning at the moment with programs like VSS either.

Thanks!


--
Gerry Hickman (London UK)
.

Relevant Pages

  • Visual Studio 6.0 Buffer Overflow Vulnerability
    ... Visual Studio 6.0 Buffer Overflow Vulnerability ... Microsoft Visual Studio 6.0 ... A Buffer Overflow Vulnerability is exists for the following file formats of affected product. ... A specially crafted project file can overwrite a stack based buffer allowing for fully EIP register control and code execution and compromise user's system. ...
    (Bugtraq)
  • Re: Change a MS Access file (mdb) to a MS Project file (mpp)
    ... Detect when a browser has submitted a form to a server, ... I need to change a Project file saved as an Access ... >> I start with a Microsoft Project file that is saved with a Microsoft ...
    (microsoft.public.vc.mfc)
  • Re: Can Project be shared on the web?
    ... I do not have a server. ... If money is no object, ... Would that allow everyone to share the same project file? ... they are on contract to you they can use Project, ...
    (microsoft.public.project)
  • [NT] Visual Studio Buffer Overflow
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... A Buffer Overflow Vulnerability exists with Visual Studio parsing of some ... malicious ".dbp" file is opened. ... A specially crafted project file can overwrite a stack based buffer ...
    (Securiteam)
  • RE: VSWebCache
    ... Thanks for your posting. ... you encounter error said "unable ot add project file ... files at a local managable location and synchorize with the web server. ... we can change the location of the web project cache to some other ...
    (microsoft.public.dotnet.framework.aspnet)