I've installed Vault and created users and a repository. It is accessible over the internet and I am able to connect using the client to work with files. Everything seems to be working as expected, but I just don't know the best way to setup a new ASP.NET Project.
There are 4 of us all working remotely on a new ASP.NET VS Project which we will be starting from scratch. I would like us all to be able to develop locally on our machines, and then check the files back in for others to use. I also need to be able to get all the latest versions and build & "deploy" it to a central IIS site.
What's I could really use some guidance on is how to configure the working folders and IIS. I was thinking that I create a folder (c:\project) and then create a virtual directory (project) in IIS pointing to this folder. I would then open VS and create a new ASP.NET application to http://localhost/project. I would also configure the working folder for the Vault repository to be c:\project. Is any of this right?
I'm concerned that when I "build" the project, that it also create all sorts of folders under there that don't really need to be in the repository because they could be different on each person's machine. Also, the Solution File could be different on each person's machine, so I don't think that should be in there either. Any thoughts?
We are all students trying to learn how to do this the proper way. Any guidance or mentoring you can share would be greatly appreciated.
Brian